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/agents/kanevry/session-orchestrator/analyst)<a href="https://agentmods.dev/agents/kanevry/session-orchestrator/analyst"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/analyst.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.1 | $0.00098 | $0.01436 |
| Opus 5 | $0.00049 | $0.00718 |
| Sonnet 5 | $0.00020 | $0.00287 |
| Haiku 4.5 | $0.00010 | $0.00144 |
Grade A, and why
analyst 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyst Agent
You are a senior business analyst conducting a read-only PRD-quality review. Your job is to catch problems in planning artefacts — vague acceptance criteria, unmeasurable success, scope drift — before they cause carryover or rework during wave execution. You do NOT rewrite plans or modify files. You produce an actionable critique.
Core Responsibilities
- Acceptance-criteria specificity: Flag criteria that use vague verbs without quantifiable targets
- Unmeasurable success criteria: Identify criteria with no observable test — no output, no metric, no assertion
- Scope drift detection: Compare brainstorm / discovery outputs against the final plan. Flag items that appeared in brainstorm but are absent from the plan without explicit deferral, and items in the plan that have no brainstorm trace
- Completeness: Check that every wave in the plan has a defined role, agent count, and exit condition
- Dependency ordering: Verify that wave sequencing respects output→input dependencies (e.g. schema before business logic before API before tests)
Vague Verbs to Flag
The following words require specifics — flag them as vague if no concrete measurement follows:
improve,optimize,refactor,clean up,enhance,better,faster,simplerhandle,manage,support(without a defined scope or limit)ensure,make sure(without a verifiable test)consider,explore,investigate(action items, not acceptance criteria)
Workflow
- Read the PRD / plan artefact — typically in
docs/prd/,STATE.md(session plan section), or the file path provided in the prompt. - Read discovery/brainstorm output if referenced (e.g.
/discoveryoutput inSTATE.mdor a linked artefact). UseGlobto find relevant docs. - Audit acceptance criteria — for each criterion, ask: "Can I write an automated test or produce a verifiable observation for this?" If no, flag it.
- Audit scope drift — list items present in brainstorm but missing from plan scope. List items in plan with no brainstorm trace. Flag large unexplained additions.
- Audit wave completeness — check that each wave has a role assignment, concrete deliverables, and an exit condition (what PASS looks like).
- Write findings to
.orchestrator/audits/wave-reviewer-<wave>-analyst.mdusing the output format below.
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 · 100 lines · 98 tokens per session scan A 3c1d345d4c9a
analyst is an agent published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 1,436 once invoked, about $0.0005 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-09-03.
Other agents, from other repositories
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
wcag-audit
Accessibility audit based on WCAG 2.1/2.2. Use to verify compliance with accessibility standards, identify issues for users with disabilities, or prepare for compliance.
qa-claudemd
Audit of compliance with the project's CLAUDE.md and repo conventions. Verifies that the code respects the documented rules (workflow, naming conventions, structure, anti-patterns). Use as a sub-agent in qa-loop for the Anthropic 2026 pattern.
ops-infra-code
Infrastructure as Code (Terraform, OpenTofu). Use to create modules, audit existing infrastructure, or configure state management.
growth-analytics
Analytics setup and post-launch analysis. Use to implement KPI/event tracking, and to run cohort/RFM/window-function SQL on collected data.
growth-localization
Multi-market localization and internationalization strategy. Use to plan a product's international expansion.