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/Kanevry/session-orchestratorWrote 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/kanevry/session-orchestrator/repo-audit)<a href="https://agentmods.dev/commands/kanevry/session-orchestrator/repo-audit"><img src="https://agentmods.dev/badge/commands/kanevry/session-orchestrator/repo-audit/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/kanevry/session-orchestrator/repo-audit"><img src="https://agentmods.dev/badge/commands/kanevry/session-orchestrator/repo-audit.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.00180 | $0.00305 |
| Opus 5.5 | $0.00072 | $0.00122 |
| Sonnet 5.5 | $0.00036 | $0.00061 |
| Haiku 4.5 | $0.00018 | $0.00030 |
Grade A, and why
repo-audit 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
/repo-audit
Use the Session Orchestrator skill definition at skills/repo-audit/SKILL.md.
Arguments: $ARGUMENTS
Read that skill file and follow it exactly. When it references $ARGUMENTS, substitute the arguments above. Keep all Session Orchestrator platform fallbacks intact.
Cursor has no Skill tool. When the skill says to invoke another skill, Read skills/<skill-name>/SKILL.md and follow it. Supporting files (soul.md, phase docs) live in that same skills/<skill-name>/ directory.
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 Changed · +168 tokens per session 8aec8bb32cd4
- 1mo ago First seen · 14 lines · 12 tokens per session scan A 3238621877ca
repo-audit is a command published in the GitHub repository Kanevry/session-orchestrator (52 stars, last pushed yesterday), licensed MIT. It adds 180 tokens to every session and 305 once invoked, about $0.0007 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-30.
Other commands, from other repositories
app-audit
Grade an existing app against the Mobify Studio House KB and Axiom standards — fan out the specialist auditors, produce a severity-ranked gap report, build a remediation backlog, then fix (safe fixes automatically, risky changes only with your approval).
app-review
Run code review on a specific branch or open PR-equivalent.
cost-estimate
Estimate a target's tokens, agent-compute time, and (when grounded) cost before it runs — the prospective sibling of /cost-capture. Dispatches the read-only cost-estimator agent, validates the returned record, and writes it after you dispose.
harness-sync
Detect drift across all push-direction control surfaces, present the full picture, and apply the user's selected fixes via the existing primitives — single human-instigated entry point for keeping convention files in sync with HARNESS.md. ONBOARDING.md staleness is surfaced but not auto-fixed; users run…
harness-affordance
Manage the project's affordance inventory — declared tools the agent can invoke, the identity each tool runs under, and the audit trail each tool produces. Subcommands - discover (scan config to produce a draft inventory), add (promote a draft into HARNESS.md with governance metadata), review (re-validate one…
cost-capture
Capture AI tool cost data — guide through provider dashboards, record spend and token usage, compare to previous snapshot, update MODELROUTING.md.