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/choxos/BiostatAgentWrote 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/choxos/biostatagent/itc-analysis)<a href="https://agentmods.dev/commands/choxos/biostatagent/itc-analysis"><img src="https://agentmods.dev/badge/commands/choxos/biostatagent/itc-analysis/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/choxos/biostatagent/itc-analysis"><img src="https://agentmods.dev/badge/commands/choxos/biostatagent/itc-analysis.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.00031 | $0.02465 |
| Opus 5.5 | $0.00012 | $0.00986 |
| Sonnet 5.5 | $0.00006 | $0.00493 |
| Haiku 4.5 | $0.00003 | $0.00247 |
Grade A, and why
itc-analysis 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.
How it starts
The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ITC Analysis - Multi-Agent Evidence Synthesis Orchestration
Design and execute a complete indirect treatment comparison analysis for: $ARGUMENTS
Thinking
This workflow orchestrates multiple specialized agents to conduct rigorous ITC analysis following NICE DSU guidance and tidy modelling principles. The approach emphasizes:
- Phase-based coordination: Each phase builds upon previous outputs with clear handoffs
- Method-appropriate specialists: Matching the right expert to the analytical task
- Assumption transparency: Explicit checking and documentation of all assumptions
- Reproducibility: Complete documentation for replication
- Sensitivity analysis: Multiple approaches to validate findings
The multi-agent approach ensures each aspect is handled by domain experts:
- ITC Architect selects methodology
- Appropriate specialists execute analysis
- Code Reviewer validates implementation
Phase 1: Evidence Assessment & Method Selection
Deliverables:
-
Evidence mapping:
- Available studies and their characteristics
- IPD vs AgD availability
- Network structure and connectivity
- Treatment comparisons of interest
-
Population assessment:
- Key population characteristics across studies
- Potential effect modifiers
- Population differences requiring adjustment
-
Assumption evaluation:
- Transitivity assessment (for NMA)
- Effect modifier identification (for MAIC/STC)
- Data requirements for each method
-
Method recommendation:
- Primary recommended method with justification
- Alternative methods for sensitivity
- Package recommendations (meta, netmeta, maicplus, stc, multinma)
-
Analysis plan outline:
- Key analyses to perform
- Sensitivity analyses needed
- Reporting requirements
Provide clear rationale for method selection referencing NICE DSU TSD guidance.
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 First seen · 396 lines · 31 tokens per session scan A bec1dde67022
itc-analysis is a command published in the GitHub repository choxos/BiostatAgent (12 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 2,465 once invoked, about $0.0001 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
openehr-explain
One-stop router that explains or looks up any openEHR thing — auto-detects an archetype, a template, an RM/AM/BASE type, an RM structural concept, an ADL idiom, an AQL query or keyword, or a terminology code (replaces /archetype-explain, /template-explain, /type-spec, /rm-structure, /adl-idiom, /terminology).
create-scene
Create a single animated scene for mathematical visualization.
srs-sm
Draft and QC the Supplementary Materials: scope approval → SM writing → figure QC for SM figures.
ars-lit-review
ARS academic-paper lit-review mode — annotated bibliography in paper format.
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.