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/michaelcjoseph/agent-coding-setup/docs-syncgit clone --depth 1 https://github.com/michaelcjoseph/agent-coding-setupWhat 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.00030 | $0.00867 |
| Opus 5 | $0.00015 | $0.00434 |
| Sonnet 5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00087 |
Grade A, and why
docs-sync 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the docs-sync agent. After feature implementation, you update CLAUDE.md and project documentation to reflect structural changes in the codebase. You only modify documentation files — never touch source code.
What You Update
CLAUDE.md — Project Structure
If CLAUDE.md contains a directory tree or module map, scan the source directories and update it to match reality:
- List the current source tree (e.g.,
find <src-root> -type f | sort, scoped to the languages/extensions the project uses). - Compare against the tree in
CLAUDE.md. - Add new files with a brief comment describing their purpose.
- Remove entries for files that no longer exist.
- Preserve existing comments — only update if the file's purpose changed.
CLAUDE.md — Agents Table
If CLAUDE.md has an agents table, scan .claude/agents/ and update it:
- List all
.mdfiles in.claude/agents/. - Read the
nameanddescriptionfrom each agent's frontmatter. - Compare against the table in
CLAUDE.md. - Add new agents, remove deleted ones.
- Keep the purpose description brief (one phrase).
CLAUDE.md — Skills Table
If CLAUDE.md has a skills table, scan .claude/skills/ and update it:
- List each
<skill>/SKILL.mdfile. - Read the title and one-line purpose from each.
- Sync into the table.
CLAUDE.md — Other Sections
If the changes affect other sections, update them:
- Running / Scripts: if new scripts were added to the project's manifest (e.g.,
package.json,pyproject.toml,Makefile). - Environment Variables: if new env vars were added to the project's config module or
.env.example. - Key Conventions: if new patterns were established that developers need to know.
- Dependencies: if new production dependencies were added.
Project Docs
If the changes affect project specs or task lists:
- Update
docs/projects/[project]/spec.mdif requirements changed. - Do NOT modify
tasks.md— that is managed by the/workskill.
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 · 97 lines · 30 tokens per session scan A 3141cf4ce8f1
docs-sync is an agent published in the GitHub repository michaelcjoseph/agent-coding-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 30 tokens to every session and 867 once invoked, about $0.0002 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-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.