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 commands/guilhermegouw/context-driven-documentation/sync-docsgit clone --depth 1 https://github.com/guilhermegouw/context-driven-documentationWhat 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.04254 |
| Opus 5 | $0.00000 | $0.02127 |
| Sonnet 5 | $0.00000 | $0.00851 |
| Haiku 4.5 | $0.00000 | $0.00425 |
Grade A, and why
sync-docs 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 712 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Intelligent documentation synchronization allowed-tools: Bash(cat:*)
🌍 Project Language Configuration
Detecting configured language from .cdd/config.yaml:
!cat .cdd/config.yaml | grep "language:" || echo "language: en"
CRITICAL STARTUP LANGUAGE RULE
Look at the language configuration detected above:
- ✅ If you see
language: pt-br→ START your FIRST message in Portuguese (PT-BR) - ✅ If you see
language: en→ START your FIRST message in English
Examples of correct startup:
When config shows language: pt-br:
📚 Analisando implementação arquivada para sincronizar documentação...
When config shows language: en:
📚 Analyzing archived implementation to sync documentation...
LANGUAGE MATCHING RULE (After Startup)
After your first message: Always respond in the same language the user writes to you.
Behavior:
- If user writes in English → Continue in English
- If user writes in Portuguese (PT-BR) → Continue in Portuguese
- User can switch languages mid-conversation, and you adapt
When generating file content (documentation files): Always use the template language that matches the .cdd/config.yaml language setting, regardless of what language the conversation is in.
Key Points:
- First message: Use language from config.yaml
- Conversation: Match user's language dynamically
- Generated files: Always use language from config.yaml
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.
- 2d ago First seen · 712 lines · 0 tokens per session scan A 1f4f0b7cd91a
sync-docs is a command published in the GitHub repository guilhermegouw/context-driven-documentation (5 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,254 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.