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/sandeep-alluru/rulegraph/testgit clone --depth 1 https://github.com/sandeep-alluru/rulegraphWrote 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/sandeep-alluru/rulegraph/test)<a href="https://agentmods.dev/commands/sandeep-alluru/rulegraph/test"><img src="https://agentmods.dev/badge/commands/sandeep-alluru/rulegraph/test.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.00000 | $0.00157 |
| Opus 5 | $0.00000 | $0.00078 |
| Sonnet 5 | $0.00000 | $0.00031 |
| Haiku 4.5 | $0.00000 | $0.00016 |
Grade A, and why
test 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 3d 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.
This is a copy
100% identical to test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Run the full test suite with coverage and report results.
Steps:
- Run:
make test(equivalent to:pytest tests/ --cov=<name> --cov-report=term-missing) - Report:
- Total tests, passed, failed, skipped
- Coverage percentage — flag if below 85%
- Any failing tests: show the test name, error message, and the relevant source line
- If any tests fail, diagnose the root cause before suggesting a fix:
- Is it a logic error in the implementation?
- Is it a test that needs updating due to an intentional behavior change?
- Is it a missing edge case?
- Do NOT suggest disabling or skipping tests to make the suite pass.
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.
- 3d ago First seen · 15 lines · 0 tokens per session scan A 737c346e7e7c
test is a command published in the GitHub repository sandeep-alluru/rulegraph (0 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 157 tokens. A static security scan graded it A with 0 findings. It is 100% identical to test, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
export
Export a knowledge abstract to an Obsidian vault — a folder of Markdown notes linked by [[wikilinks]].
memory-search
Search agent memory + learned patterns for cross-session context relevant to $ARGUMENTS.
bootstrap-memory
RUN { git ls-files; git ls-files --others --exclude-standard; } 2>/dev/null | sort -u | xargs wc -l 2>/dev/null | sort -rn | head -150 READ README.md.
maestro-guard
Manage editing boundary restrictions.
maestro-issue
Intent-driven issue lifecycle management — describe what you want in natural language (报告一个 bug / 列出开放 issue / 关掉 ISS-xxx / 关联到 task / 扫描发现问题) and the workflow routes to the right operation. Operates on .workflow/issues/. 知识管理走 /maestro-knowledge；knowhow 沉淀走 /maestro-knowhow；约束规则走 /maestro-spec。Triggers on "issue 管理"…
twining:export
Export Twining state as markdown for context handoff or archival.