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/jsohi/app-trading-engine/compliancegit clone --depth 1 https://github.com/jsohi/app-trading-engineWrote 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/jsohi/app-trading-engine/compliance)<a href="https://agentmods.dev/commands/jsohi/app-trading-engine/compliance"><img src="https://agentmods.dev/badge/commands/jsohi/app-trading-engine/compliance.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.00009 | $0.03879 |
| Opus 5 | $0.00005 | $0.01939 |
| Sonnet 5 | $0.00002 | $0.00776 |
| Haiku 4.5 | $0.00001 | $0.00388 |
Grade A, and why
compliance 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 5d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance — Industry-Standard Scoring Dashboard
Score the codebase against 13 weighted industry metrics for a production trading engine. Produces a single percentage (0-100%) and a tabular report with per-category breakdown.
MANDATORY RULES
- NEVER mark anything as "accepted" or "out of scope" — dev phase means everything must meet the target.
- Score the ENTIRE codebase — not just the current branch's changes. This is a health check on all production code.
- Run ALL automated scans — do not skip any scan even if you "already know" the result.
- Spawn BOTH review agents — Agent A (Documentation + Thread-Safety) and Agent B (Allocation + Autoboxing +
final var). - NEVER estimate, guess, or approximate a score — every number in the report must come from an actual command execution. Never write "~", "approximately", "estimated", or "about". If a scan wasn't run, report "NOT MEASURED" instead of guessing.
Scoring Rubric — 13 Categories, 100 Points
| # | Category | Weight | Target | Scope |
|---|---|---|---|---|
| 1 | Test Coverage (line + branch) | 15 | >= 80% combined | All Java modules |
| 2 | Zero-Allocation Compliance | 14 | 100% | Hot-path: cluster, gateway, orchestrator, pricing-service, projections |
| 3 | Code Documentation Coverage | 12 | 100% class + method | All production Java |
| 4 | Determinism Compliance | 10 | 100% | cluster module |
| 5 | Collection Compliance | 8 | 100% | Hot-path modules |
| 6 | Autoboxing Compliance | 8 | 100% | Hot-path modules |
| 7 | FIX Protocol Compliance | 7 | 100% | trading-schema.xml |
| 8 | Formatting Compliance | 5 | Pass | All Java |
| 9 | Logging Compliance | 5 | 100% | All modules |
| 10 | Clock Discipline | 5 | 100% | All non-test modules |
| 11 | final var Usage |
4 | >= 90% | All production Java |
| 12 | Security (OWASP CVE) | 4 | 0 findings >= 7.0 CVSS | Full dependency tree |
| 13 | Thread-Safety Documentation | 3 | >= 90% | All production public classes |
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.
- 5d ago First seen · 327 lines · 9 tokens per session scan A cc54d5ac2c70
compliance is a command published in the GitHub repository jsohi/app-trading-engine (2 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 3,879 once invoked, about $0.0000 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.