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/leoyang183/sync-agents-settings/report-schemagit clone --depth 1 https://github.com/Leoyang183/sync-agents-settingsWrote 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/leoyang183/sync-agents-settings/report-schema)<a href="https://agentmods.dev/commands/leoyang183/sync-agents-settings/report-schema"><img src="https://agentmods.dev/badge/commands/leoyang183/sync-agents-settings/report-schema.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.00161 |
| Opus 5 | $0.00006 | $0.00081 |
| Sonnet 5 | $0.00002 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
report-schema 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 4d 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
Generate report schema markdown from code metadata (COMMAND_REQUIRED_FIELDS) and print to stdout or write to file.
Usage
# Print to stdout
npx sync-agents-settings report-schema
# Write to docs file
npx sync-agents-settings report-schema --write docs/report-schema.md
# CI check: fail if docs/report-schema.md is stale or missing
npx sync-agents-settings report-schema --check
Notes
- Use this command after changing report payload fields or parser validation rules.
- The generated file should include the "Required Fields (Generated)" section.
--checkexits with code1when target schema file is missing or outdated.
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.
- 4d ago First seen · 26 lines · 12 tokens per session scan A 2010093b9fa3
report-schema is a command published in the GitHub repository Leoyang183/sync-agents-settings (8 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 161 once invoked, about $0.0001 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 commands, from other repositories
om-review-brief
Generate a performance review context transfer document from vault data. Supports manager version (PO-friendly) and peer version (project-focused).
wiki-update
Update a single wiki page in place without running a full re-ingest.
wiki-ingest
Ingest a source document (or folder) into the llmwiki.
wiki-export-marp
Generate a Marp slide deck from wiki content matching a topic.
handoff
Generate context handoff document for session continuity.
anti-pattern-czar
You are the Anti-Pattern Czar, an expert at identifying and fixing error handling anti-patterns.