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.
git clone --depth 1 https://github.com/JOndarza/loadoutWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/jondarza/loadout/docs-sync)<a href="https://agentmods.dev/commands/jondarza/loadout/docs-sync"><img src="https://agentmods.dev/badge/commands/jondarza/loadout/docs-sync/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jondarza/loadout/docs-sync"><img src="https://agentmods.dev/badge/commands/jondarza/loadout/docs-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00013 | $0.00354 |
| Opus 5.5 | $0.00005 | $0.00142 |
| Sonnet 5.5 | $0.00003 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00035 |
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 1mo 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
Run the docs-architect skill in sync mode.
- Find the last commit that touched
docs/or.claude/rules/:git log --oneline --all -- docs/ .claude/rules/ | head -1 - List all files changed since that commit:
git diff --name-only <last>..HEAD - Delegate the file-change analysis to the
doc-explorersubagent (isolated context) if the list is longer than 20 files. - Map changed code files to affected docs and rules:
*.csproj,package.json,Cargo.toml→.claude/rules/tech-stack.md+docs/tech-stack.mddocker-compose*,Dockerfile*,.env*→docs/deployment.md- Controllers / routes / endpoints →
.claude/rules/api.md+docs/api-contracts.md - Entities / migrations →
.claude/rules/database.md+docs/database-schema.md - Domain layer / patterns / middleware →
.claude/rules/architecture.md+docs/architecture.md - Naming / validators / test files →
.claude/rules/coding-rules.md+docs/coding-rules.md
- Output a sync report listing docs-needing-update vs. docs-still-current.
- Ask the user: update affected docs now? [yes / pick individually / skip]
- If yes, update each affected rule AND doc file (dual update).
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.
- 1mo ago First seen · 22 lines · 13 tokens per session scan A 59320437b678
docs-sync is a command published in the GitHub repository JOndarza/loadout (3 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 354 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
README
Git workflow and quality assurance commands for the claude-skills repository.
benchmark
Design and coordinate a reproducible Java performance test.
profile
Coordinate a reproducible Java profiling and optimization lifecycle.
update-issue
Update an issue description with structured, evidence-backed content.
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
earnings
Post-earnings analysis for a stock — fast in-chat summary card by default, full Markdown research report on request.