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/choxos/biostatagent/sample-sizegit clone --depth 1 https://github.com/choxos/BiostatAgentWhat 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.00014 | $0.00625 |
| Opus 5 | $0.00007 | $0.00313 |
| Sonnet 5 | $0.00003 | $0.00125 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
sample-size 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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sample Size Determination Workflow
Overview
Find the minimum sample size (or event count) required to achieve target power across specified treatment effect scenarios.
Workflow Phases
Phase 1: Requirements
Phase 2: Search Strategy
Methods:
- Binary search: Efficient for single scenario
- Grid search: Better for multiple scenarios
- Compound criteria: Min power across scenarios ≥ target
Phase 3: Validation
Success Criteria
- Sample size found meeting target power
- Results validated with high-precision simulation
- Sensitivity across scenarios documented
- Clear recommendation with rationale
Final Deliverables
- Recommended sample size with justification
- Power at recommended N for all scenarios
- Sample size sensitivity table
- Optimal interval analysis
- R code for replication
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.
- 2d ago First seen · 94 lines · 14 tokens per session scan A a6884667e8ad
sample-size is a command published in the GitHub repository choxos/BiostatAgent (11 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 625 once invoked, about $0.0001 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-30.
Other commands, from other repositories
pr-review
You are reviewing a pull request. Your job is to audit the changes and produce a structured review with two clearly separated sections: In-Scope items (things that should be fixed in this PR before merge) and Out-of-Scope items (things worth addressing but belonging in separate issues).
pr
Analyse the diff between the current branch and main, then open a pull request using the GitHub CLI (gh).
graphiti-health
Display unified real-time health status for Neo4j Aura and Graphiti services.
scaffold-fastmcp-v2
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-aura-stats
Generate production graph statistics for Neo4j Aura analytics and capacity planning.
scaffold-fastmcp
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.