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 skills/hoophq/hoop/test-plannpx skills add hoophq/hoop --skill test-plangit clone --depth 1 https://github.com/hoophq/hoopWrote 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/skills/hoophq/hoop/test-plan)<a href="https://agentmods.dev/skills/hoophq/hoop/test-plan"><img src="https://agentmods.dev/badge/skills/hoophq/hoop/test-plan.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.00044 | $0.00403 |
| Opus 5 | $0.00022 | $0.00201 |
| Sonnet 5 | $0.00009 | $0.00081 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
test-plan 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 6d 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
Generate a test plan for the current changes
Goal: a teammate (or a QA agent) must be able to validate this change without asking anything. This is the team's standard for every PR.
Steps
- Diff the branch against main:
git diff main...HEAD --statthen read the changed files' diffs. - Identify what is observable from outside: which API response, CLI
behavior (
hoop connect/hoop exec/ proxy flow), gateway/agent interaction, orwebapp_v2screen changed. - Write a
## How to testsection in markdown:- Setup: exact commands — see
DEV.md(make run-dev, Postgres viamake run-dev-postgres, agent,webapp_v2:npm run dev). Only what this change needs. - Steps: numbered, copy-pasteable commands or precise UI actions.
- Expected: the observable result per step — literal output where possible (API status + body fields, CLI output, what the screen shows).
- Regression check: 1-2 quick checks that the closest existing behavior still works.
- Setup: exact commands — see
- Cover the negative path too (permission denied, invalid input, guardrail still blocking after a fix).
- If a step cannot be validated locally (needs enterprise libhoop, IDP, cloud resources), say so explicitly and state what environment is needed — never leave silent gaps.
Output the section ready to paste into the PR body (or update the open PR
with gh pr edit --body-file if asked).
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.
- 6d ago First seen · 35 lines · 44 tokens per session scan A 82489abb1e80
test-plan is a skill published in the GitHub repository hoophq/hoop (807 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 403 once invoked, about $0.0002 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 skills, from other repositories
imaging-data-commons
Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.
geo-database
Access NCBI GEO for gene expression/genomics data. Search/download microarray and RNA-seq datasets (GSE, GSM, GPL), retrieve SOFT/Matrix files, for transcriptomics and expression analysis.
brenda-database
Access BRENDA enzyme database via SOAP API. Retrieve kinetic parameters (Km, kcat), reaction equations, organism data, and substrate-specific enzyme information for biochemical research and metabolic pathway analysis.
clinpgx-database
Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.
gwas-database
Query NHGRI-EBI GWAS Catalog for SNP-trait associations. Search variants by rs ID, disease/trait, gene, retrieve p-values and summary statistics, for genetic epidemiology and polygenic risk scores.
string-database
Query STRING API for protein-protein interactions (59M proteins, 20B interactions). Network analysis, GO/KEGG enrichment, interaction discovery, 5000+ species, for systems biology.