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 skills add matt-bat/agent-command-center --skill effective-testing-methodsgit clone --depth 1 https://github.com/matt-bat/agent-command-centerWrote 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/matt-bat/agent-command-center/effective-testing-methods)<a href="https://agentmods.dev/skills/matt-bat/agent-command-center/effective-testing-methods"><img src="https://agentmods.dev/badge/skills/matt-bat/agent-command-center/effective-testing-methods/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/skills/matt-bat/agent-command-center/effective-testing-methods"><img src="https://agentmods.dev/badge/skills/matt-bat/agent-command-center/effective-testing-methods.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.00058 | $0.00810 |
| Opus 5.5 | $0.00023 | $0.00324 |
| Sonnet 5.5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
effective-testing-methods 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 99 lines · 58 tokens per session scan A 7afeb704b34e
effective-testing-methods is a skill published in the GitHub repository matt-bat/agent-command-center (4 stars, last pushed 1mo ago), with no licence file. It adds 58 tokens to every session and 810 once invoked, about $0.0002 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-31.
Other skills, from other repositories
speq-implement
Orchestrate implementation of a reviewed plan: task breakdown, TDD sub-agents, code review, and verification report. Use when the user asks to implement, build, or execute a plan under specs/plans/ — after /speq-plan, before /speq-record. Arg: .
speq-planning
Plan-authoring workflow — spec delta authoring, test mapping, plan.md/decision-log.md generation, expert-task tagging, headless escalation, and revision mode. Use when authoring a plan.
speq-implement-pr
Headless follow-up to /speq-plan-pr. Continues a plan on its feat/plan-name branch and runs it end-to-end: implements via /speq-implement, bumps the version, commits and pushes, runs the real test suites, records only if green, then opens/updates the PR and marks it ready. Resumes from the PR Lifecycle checkpoint in…
speq-code-guardrails
TDD cycle and code quality guardrails — failing-test-first, evidence, dependency, error-handling, and test-quality rules. Used by speq implementer and reviewer agents during a speq implement run. Not for general coding.
mine-plan-review
Strictly review one implemented repository plan against AGENTS.md, architecture, the immutable plan, implementation commits, real runtime behavior, verification evidence, and downstream contracts. Use when the user invokes the host-specific mine-plan-review skill with a plan path, asks whether a plan can be accepted…
crucible
Write solid unit tests using property-based testing and mutation testing. Use whenever unit tests are being written, fixed, audited, or reviewed in a TypeScript project; whether the user asks directly or test-writing occurs as a step inside another workflow (TDD, feature implementation, bug fixing, code review). Also…