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 skills/sioyooo/repogrammar/agent-integrationnpx skills add SioYooo/RepoGrammar --skill agent-integrationgit clone --depth 1 https://github.com/SioYooo/RepoGrammarWhat 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.00025 | $0.00413 |
| Opus 5 | $0.00013 | $0.00206 |
| Sonnet 5 | $0.00005 | $0.00083 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
agent-integration 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
Purpose
Keep machine-level agent integration safe, reversible, and scoped.
Trigger conditions
Use when editing repogrammar install, repogrammar uninstall, MCP
configuration writes, installation receipts, or agent instruction-file edits.
Required reading
docs/specifications/installation.mddocs/decisions/ADR-0007-safe-install-progress-telemetry.mddocs/specifications/mcp-api.md
Preconditions
- Identify target agent and scope.
- Confirm dry-run and print-config behavior are available.
- Confirm consuming repositories are not forced to mirror RepoGrammar's own root guide policy.
Step-by-step procedure
- Detect supported agents.
- Prefer native agent configuration commands where available.
- Preserve unknown config fields.
- Refuse malformed config by default.
- Back up before approved repair.
- Write atomically and reparse after writing.
- Store a reversible receipt.
- Validate MCP integration with a self-test.
- Only modify instruction files with marker fences and explicit consent.
- Never create or delete repository-local
.repogrammar/indexes frominstalloruninstall; project state belongs toinitanduninit.
Required verification
Run installer parsing tests, self-test validation tests when implemented, and the full repository verification suite.
Documentation updates
Update docs/specifications/installation.md, README, CHANGELOG, and MCP docs
as needed.
Commit requirements
Never commit machine-local receipts or generated user config. Commit tests and docs with installer behavior.
Completion report
Report target agents, scopes, dry-run behavior, receipt behavior, and any configuration that remains unsupported.
Failure and rollback handling
If config is malformed or unknown ownership cannot be proven, do not write. Report the blocker and leave user configuration untouched.
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 · 66 lines · 25 tokens per session scan A 800ed99bbfb8
agent-integration is a skill published in the GitHub repository SioYooo/RepoGrammar (0 stars, last pushed 19d ago), licensed MIT. It adds 25 tokens to every session and 413 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 skills, from other repositories
od-contribute
One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship…
clinical-case-report
Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds"…
critique
Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks…
github-dashboard
GitHub repository analytics dashboard — stars, forks, contributors, issues, pull requests, recent activity, and top contributors. Use when the brief asks for a GitHub repo dashboard, open-source growth report, repository health page, or GitHub analytics view.
dating-web
A consumer-feeling dating / matchmaking dashboard — left rail navigation, ticker bar of community signals, headline KPIs, a 30-day mutual-matches bar chart, and a match-rate trend block. Editorial typography, restrained accent. Use when the brief asks for a "dating site", "matchmaking", "community dashboard", "social…
dcf-valuation
Discounted cash flow valuation and intrinsic value analysis for public companies. Use when the brief asks for DCF, fair value, intrinsic value, price target, undervalued or overvalued analysis, or "what is this company worth?".