Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/kerim/zotero-code-execution/claude-mdgit clone --depth 1 https://github.com/kerim/zotero-code-executionWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00286 | $0.00286 |
| Opus 5 | $0.00143 | $0.00143 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
zotero-code-execution CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Development Instructions for zotero-code-execution
Skill Development Workflow
This project follows the standardized skill workflow. The skill files are in the skill/ subfolder, which is symlinked to ~/.claude/skills/zotero-mcp-code/.
Important Rules
- Only edit files in the
skill/folder - Never edit~/.claude/skills/directly (it's a symlink to this folder) - Update README.md if functionality changes
- Ask user to review changes before committing
- Commit and push after user approval (if remote exists)
File Structure
zotero-code-execution/
├── skill/ # Symlinked to ~/.claude/skills/zotero-mcp-code/
│ └── SKILL.md # The actual skill definition
├── *.py # Python library and scripts
├── README.md # GitHub install instructions
└── CLAUDE.md # This file - workflow instructions
Before Committing
- Changes are in
skill/folder only - README.md updated if needed
- User has reviewed changes
- Version number updated (if applicable)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 33 lines · 286 tokens per session scan A 850817c70975
zotero-code-execution CLAUDE.md is an instructions file published in the GitHub repository kerim/zotero-code-execution (59 stars, last pushed 7mo ago), licensed MIT. It adds 286 tokens to every session, about $0.0014 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
daisyui code_generation_with_git.instructions.md
Instructions for saadeghi/daisyui, covering activation, initial setup, development loop, error handling and session end.
planning-with-files AGENTS.md
AGENTS.md instructions for OthmanAdi/planning-with-files, covering agents.md — planning-with-files agent reference card, commit rules, release checklist (12 steps), version bump scope and changelog format.
mq commit.instructions.md
Instructions for harehare/mq: Use the following format for commit messages.
sprites-ex CLAUDE.md
Instructions for superfly/sprites-ex, covering sprites elixir sdk, quick reference, common commands, install dependencies and compile.
stiletto CLAUDE.md
Instructions for benjamin-bader/stiletto, covering stiletto — contributor & agent guide, commit messages: conventional commits (required), breaking changes, examples and how releases work.
crow CLAUDE.md
Instructions for kh0pper/crow, covering claude.md, working with this repo, network exposure invariant, maintaining claude.md vs crow.md and where to find things.