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/tmj-90/gaffer/run-testsnpx skills add tmj-90/gaffer --skill run-testsgit clone --depth 1 https://github.com/tmj-90/gafferWrote 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/tmj-90/gaffer/run-tests)<a href="https://agentmods.dev/skills/tmj-90/gaffer/run-tests"><img src="https://agentmods.dev/badge/skills/tmj-90/gaffer/run-tests.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 | $0.00053 | $0.00410 |
| Opus 5 | $0.00026 | $0.00205 |
| Sonnet 5 | $0.00011 | $0.00082 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
run-tests 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 4d 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
Run the test suite
Run the repo's existing test command, report the real result, and evidence it. Do not introduce a new runner — use what the project already uses.
Steps
- Find the test command from the context packet's verification commands
(e.g.
pnpm test,npm test,pytest,go test ./...,mvn test). If the packet is silent, detect it from the manifest (package.jsonscripts,pyproject.toml,go.mod,pom.xml). Use the project script, not the underlying tool directly. - Run the full suite (or the scoped subset the ticket names). Capture the exact command and the pass/fail summary, including counts (passed/failed/skipped).
- If tests fail, read the failures. Fix only what the ticket scopes; if a failure is unrelated and pre-existing, note it — do not paper over it or delete the test.
- Re-run until green (or until you confirm a failure is out of scope and blocking).
- Evidence: the exact command and its passing summary. Then use the
record-evidenceskill to recordtest_outputagainst the AC and submit for review.
Rules
- Report the true result — never claim "tests pass" without a run in this session.
- Don't skip or delete failing tests to go green; fix the cause or mark blocked.
- Don't add a new test framework; match the repo's runner.
- Run on a branch (the
create-branchskill), never a protected branch.
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.
- 4d ago First seen · 33 lines · 53 tokens per session scan A c07284f8e6fa
run-tests is a skill published in the GitHub repository tmj-90/gaffer (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 53 tokens to every session and 410 once invoked, about $0.0003 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 skills, from other repositories
skill-creator
Create or update AnkaLoop skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. This skill should be used when users want to create a new skill (or update an existing skill) that extends AnkaLoop's capabilities with specialized knowledge, workflows, or tool integrations.
ai-engineer
Expert knowledge in AI/ML development, model deployment, and MLOps practices.
gh-ci-analyzer
使用 gh CLI 分析 GitHub Actions CI 日志，提供结构化的故障诊断和报告.
security-best-practices
Security best practices and vulnerability prevention guidelines.
react-developer
Expert knowledge in React development, hooks, state management, and modern React patterns.
gh-pr-review
Review GitHub Pull Requests using the gh CLI. Use when a user asks to review a PR, perform code review, check a pull request, or provide feedback on proposed changes. Triggers on phrases like "review PR", "review pull request", "check PR", "code review".