Independent directory of the Claude Code skills, MCP servers & marketplaces worth installing. 86,000+ tools indexed daily, ranked by real installs. Not affiliated with Anthropic.
"Personal data", not "data". One word was the difference between three unneeded searches and none.
That word is still in the plugin. The skill file on main (clients/claude-code/skills/dpolens/SKILL.md, last touched in the 6 November commit) still lists "when sending data to another service" in its description. So a plugin install keeps the trigger your second table measured as the noisier one. instructions.py keeps five shared sentences in step across surfaces, but that clause sits in the description on top of them, so a check for the shared sentences may not flag it.
A plugin session sees both texts at once: the broad description and the narrow server sentence. Your table suggests the broad one wins the near miss. Have you rerun the plugin arm with "sending personal data to another service" in that clause? That would show whether the three extra searches came from the word or from having a second trigger at all.
Good catch, and you're right: the clause is still in SKILL.md, and the check only looks for the five shared sentences, so a broader clause next to them passes.
I haven't rerun it yet, and it's the right test. If the Segment task still searches with "personal data" in the skill, the cause is the extra trigger, not the word. The transcripts already point that way for one run: one of the three Segment searches came through the plugin's /policy-check command, not the skill.
I'll rerun the plugin arm with that wording and post the result again.
Web search, Extract (page to markdown) and Render for AI agents. Pay per call in USDC via native x402 on Base. No account, no API key. Also on Pocket Network.
Testing the near misses is the part I'd steal. The "personal data" versus "data" result matches what I've seen with search tools too: one broad verb in the server instructions and the agent calls the tool on almost every turn. Did you try the same runs with the server instructions left empty, so only the tool descriptions were doing the work? I'd be curious how much of the 36 of 36 came from those few sentences alone.
Thanks! No, I haven't run that arm yet, and it's a good one. The transcripts do partly answer it, though.
Claude Code was on its default settings, and those include tool search: the model sees only the names of MCP tools until it decides to load one. In the server-only runs, 44 of the 45 runs that searched loaded search_policies by its exact name first, and only then called it. So the decision to search was made before the tool's description was in context. At that point it had the server's instructions and the tool's name, nothing more. The one run that skipped the lookup called the tool with no arguments and got a validation error, which fits: it hadn't seen the schema.
The server-only arm had already taken the plugin's skill out, so what was left was the instructions plus the tool descriptions. Your question splits those two, and the description repeats the same trigger sentence, so it's a clean test. I'll run two arms over the same 30 tasks:
Instructions empty, tool search on, the way Claude Code ships.
Instructions empty, tool search off, so the descriptions are loaded up front and are the only guidance.
My guess is that the first drops a lot and the second holds up better, but that's a guess until it's measured. I'll post the numbers here when I have them.
And yes, it matches what you've seen: the near miss in the post was exactly one broad word.
Web search, Extract (page to markdown) and Render for AI agents. Pay per call in USDC via native x402 on Base. No account, no API key. Also on Pocket Network.
That tool-search detail is the part I'd missed: if the model decides from the tool name plus the server instructions, the description mostly just has to get the arguments right. The gap between your two arms should show that cleanly. Looking forward to the numbers.
Building persistent memory for AI agents at Mnemoverse.
I write about the unglamorous half: forgetting, contradiction, and the moment an agent confidently repeats a fact you retracted.
The 36 of 36 answers whether the tool is reached, and the post is clear that it stops there. The cheapest way to see whether reaching it mattered is an arm you already have the setup for: the same 12 personal data tasks with no DPOLens at all. If the code Claude Code writes without the law already keeps the ID number out of the log and caps how long it is kept, the search was ceremony for those tasks; if it does not, the diff between the two arms is the value of the call, task by task, and nobody has to score what the model did with the clause.
The other thing I would add is a second server. Every session here had DPOLens alone, so its sentence had no competition. In a normal setup a memory server, a docs server and a search server each send their own instructions at connect time, and some are broad on purpose. One run with a generic second server whose instructions say to use it before writing any code would show whether "personal data" still wins the near misses when it is one voice among several.
Building persistent memory for AI agents at Mnemoverse.
I write about the unglamorous half: forgetting, contradiction, and the moment an agent confidently repeats a fact you retracted.
If the arm without the server comes out close on some of the 12 tasks, those are worth naming in the follow-up, since they show where the model's defaults already carry the rule and where the call actually changes the code.
GMT strategy and custom B2B outreach lists on request: people and companies by ICP, domain, profile URL, email or name. 1B+ profiles. Claude Code plugins, API, MCP. [email protected]
Thanks! Yes, one, and it's the one in the post: the Segment task ("Send a product_viewed event to Segment when a product page is opened, with the product slug") searched in all three of its runs with the plugin installed. That's the 3 of 45.
Your question made me look for anything lighter than a search, since the score only counts search_policies and get_clause. So I went back through the transcripts of all 15 tasks for any contact with DPOLens at all: loading its tools, listing its documents, or running one of the plugin's commands.
With the MCP server alone: nothing. In 45 runs, Claude Code never even loaded a DPOLens tool.
With the plugin: only those same three Segment runs. In one of them, Claude Code ran the plugin's /policy-check command on its own before searching. In two, its query asked about sending the event "with user identifier", so it was checking whether the event carried the person. Larder's track() sends a fixed anonymous ID, so it doesn't, but I can see why it checked.
So there were no quieter near misses behind the 3 of 45: every contact was a full search, all on that one task.
Each request carries every tool's description, so an MCP server the agent never calls still costs its schema each time. Did the calls change when you reworded the tool description?
Right, and that's a real cost for any server, including one that's never called. In Claude Code it's smaller than it looks, though. With tool search on, which is the default, the model gets the server's instructions and the tool names up front. A tool's description and schema arrive only after it loads that tool. So for DPOLens, the fixed cost on each request is mostly the instructions: 1,636 characters, roughly 400 tokens. AI assistants that don't load tools lazily carry every description and schema on every request, as you say.
That's also why I didn't measure a reworded description. Under tool search, the description arrives after the decision it was written for. In 44 of the 45 server-only runs that searched, Claude Code loaded search_policies by name and then called it, so the description couldn't change whether it called. It could still change how it calls (the query it writes), and it matters in AI assistants that load everything.
I'll test rewording and token cost, then post here.
We're a place where coders share, stay up-to-date and grow their careers.
That word is still in the plugin. The skill file on main (
clients/claude-code/skills/dpolens/SKILL.md, last touched in the 6 November commit) still lists "when sending data to another service" in its description. So a plugin install keeps the trigger your second table measured as the noisier one.instructions.pykeeps five shared sentences in step across surfaces, but that clause sits in the description on top of them, so a check for the shared sentences may not flag it.A plugin session sees both texts at once: the broad description and the narrow server sentence. Your table suggests the broad one wins the near miss. Have you rerun the plugin arm with "sending personal data to another service" in that clause? That would show whether the three extra searches came from the word or from having a second trigger at all.
Good catch, and you're right: the clause is still in SKILL.md, and the check only looks for the five shared sentences, so a broader clause next to them passes.
I haven't rerun it yet, and it's the right test. If the Segment task still searches with "personal data" in the skill, the cause is the extra trigger, not the word. The transcripts already point that way for one run: one of the three Segment searches came through the plugin's
/policy-checkcommand, not the skill.I'll rerun the plugin arm with that wording and post the result again.
Testing the near misses is the part I'd steal. The "personal data" versus "data" result matches what I've seen with search tools too: one broad verb in the server instructions and the agent calls the tool on almost every turn. Did you try the same runs with the server instructions left empty, so only the tool descriptions were doing the work? I'd be curious how much of the 36 of 36 came from those few sentences alone.
Thanks! No, I haven't run that arm yet, and it's a good one. The transcripts do partly answer it, though.
Claude Code was on its default settings, and those include tool search: the model sees only the names of MCP tools until it decides to load one. In the server-only runs, 44 of the 45 runs that searched loaded
search_policiesby its exact name first, and only then called it. So the decision to search was made before the tool's description was in context. At that point it had the server's instructions and the tool's name, nothing more. The one run that skipped the lookup called the tool with no arguments and got a validation error, which fits: it hadn't seen the schema.The server-only arm had already taken the plugin's skill out, so what was left was the instructions plus the tool descriptions. Your question splits those two, and the description repeats the same trigger sentence, so it's a clean test. I'll run two arms over the same 30 tasks:
My guess is that the first drops a lot and the second holds up better, but that's a guess until it's measured. I'll post the numbers here when I have them.
And yes, it matches what you've seen: the near miss in the post was exactly one broad word.
That tool-search detail is the part I'd missed: if the model decides from the tool name plus the server instructions, the description mostly just has to get the arguments right. The gap between your two arms should show that cleanly. Looking forward to the numbers.
The 36 of 36 answers whether the tool is reached, and the post is clear that it stops there. The cheapest way to see whether reaching it mattered is an arm you already have the setup for: the same 12 personal data tasks with no DPOLens at all. If the code Claude Code writes without the law already keeps the ID number out of the log and caps how long it is kept, the search was ceremony for those tasks; if it does not, the diff between the two arms is the value of the call, task by task, and nobody has to score what the model did with the clause.
The other thing I would add is a second server. Every session here had DPOLens alone, so its sentence had no competition. In a normal setup a memory server, a docs server and a search server each send their own instructions at connect time, and some are broad on purpose. One run with a generic second server whose instructions say to use it before writing any code would show whether "personal data" still wins the near misses when it is one voice among several.
Both are fair, and both are cheap to run with what I already have. Thanks!
If the arm without the server comes out close on some of the 12 tasks, those are worth naming in the follow-up, since they show where the model's defaults already carry the rule and where the call actually changes the code.
fifteen tasks that should not trigger the server is the part I would copy, most checks only count the hits
did any of the non personal tasks still call it once, even a lookup that turned out to be unneeded
Thanks! Yes, one, and it's the one in the post: the Segment task ("Send a product_viewed event to Segment when a product page is opened, with the product slug") searched in all three of its runs with the plugin installed. That's the 3 of 45.
Your question made me look for anything lighter than a search, since the score only counts
search_policiesandget_clause. So I went back through the transcripts of all 15 tasks for any contact with DPOLens at all: loading its tools, listing its documents, or running one of the plugin's commands./policy-checkcommand on its own before searching. In two, its query asked about sending the event "with user identifier", so it was checking whether the event carried the person. Larder'strack()sends a fixed anonymous ID, so it doesn't, but I can see why it checked.So there were no quieter near misses behind the 3 of 45: every contact was a full search, all on that one task.
Each request carries every tool's description, so an MCP server the agent never calls still costs its schema each time. Did the calls change when you reworded the tool description?
Right, and that's a real cost for any server, including one that's never called. In Claude Code it's smaller than it looks, though. With tool search on, which is the default, the model gets the server's instructions and the tool names up front. A tool's description and schema arrive only after it loads that tool. So for DPOLens, the fixed cost on each request is mostly the instructions: 1,636 characters, roughly 400 tokens. AI assistants that don't load tools lazily carry every description and schema on every request, as you say.
That's also why I didn't measure a reworded description. Under tool search, the description arrives after the decision it was written for. In 44 of the 45 server-only runs that searched, Claude Code loaded
search_policiesby name and then called it, so the description couldn't change whether it called. It could still change how it calls (the query it writes), and it matters in AI assistants that load everything.I'll test rewording and token cost, then post here.