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 agents/mistakeknot/interdoc/developmentgit clone --depth 1 https://github.com/mistakeknot/interdocWhat 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.00000 | $0.00490 |
| Opus 5 | $0.00000 | $0.00245 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
development 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 yesterday.
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 & Versioning
Development
This is Documentation-Driven
There is no source code to build or test. The "implementation" is the skill documentation and shell scripts.
To modify behavior:
- Edit
skills/interdoc/SKILL.mdto change workflows - Edit
hooks/*.shto change trigger logic - Update
README.mdfor user-facing documentation - Update
.claude-plugin/plugin.jsonfor metadata/version changes
Testing Changes
- Make changes to SKILL.md or hook files
- Commit and push to GitHub
- Run
claude plugin update interdoc@interagency-marketplaceto refresh local cache - Trigger the skill to verify behavior
See docs/TEST_PLAN.md for comprehensive test cases.
Version Management
Version is declared in .claude-plugin/plugin.json (root level).
| Change Type | Version Bump | Example |
|---|---|---|
| Bug fix, docs clarification | Patch | 4.3.0 → 4.3.1 |
| New feature, workflow change | Minor | 4.3.0 → 4.4.0 |
| Breaking change | Major | 4.3.0 → 5.0.0 |
Bump Version
After committing skill changes:
# 1. Edit plugin.json and increment version
# 2. Commit and push
git add .claude-plugin/plugin.json
git commit -m "Bump version to X.Y.Z"
git push
Update the Marketplace
The plugin is distributed via interagency-marketplace. After pushing version changes:
- Edit
~/interagency-marketplace/.claude-plugin/marketplace.json - Update the
interdocentry version - Commit and push
- Refresh local cache:
claude plugin marketplace update interagency-marketplace claude plugin update interdoc@interagency-marketplace
Commit Workflow
- Edit the relevant files (SKILL.md, hooks, etc.)
- Commit with descriptive message
- Bump version in plugin.json
- Commit version bump
- Push both commits
- Update ~/interagency-marketplace with new version
- Push marketplace changes
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.
- yesterday First seen · 68 lines · 0 tokens per session scan A b7d99b9cc25f
development is an agent published in the GitHub repository mistakeknot/interdoc (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 490 tokens. 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.