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 marcoguillermaz/Tierward --skill test-auditgit clone --depth 1 https://github.com/marcoguillermaz/TierwardWrote 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/marcoguillermaz/tierward/test-audit)<a href="https://agentmods.dev/skills/marcoguillermaz/tierward/test-audit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/test-audit/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/marcoguillermaz/tierward/test-audit"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/test-audit.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.00064 | $0.03754 |
| Opus 5 | $0.00032 | $0.01877 |
| Sonnet 5 | $0.00013 | $0.00751 |
| Haiku 4.5 | $0.00006 | $0.00375 |
Grade A, and why
test-audit 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 10d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope for v1
- Static analysis only. Parses coverage reports produced by the project's test runner. Does not execute tests, does not re-run the suite, does not query CI history.
- Flaky-test detection is deferred. Detecting non-deterministic failures requires multiple runs or CI-history access, both out of scope for the first ship. Tracked as future-work item
TEST-flake-detection. - Live flake / performance probes: revisit after real usage.
Configuration (adapt before first run)
Replace these placeholders:
[TEST_PATH]- primary location of test files (e.g.src/**/*.test.ts,tests/,spec/,Tests/,src/test/)[COVERAGE_PATH]- location of coverage reports if non-standard (e.g.coverage/lcov.info,reports/coverage.xml)[APP_SOURCE_PATH]- path to application source (for colocated-test detection) - e.g.src/,app/,lib/
Step 0 - Target resolution
Parse $ARGUMENTS for a target: or mode: token.
| Pattern | Meaning |
|---|---|
target:path:<dir> |
Audit tests under a specific directory only (e.g. target:path:src/auth) |
target:file:<glob> |
Audit files matching the glob (e.g. target:file:**/*.integration.test.ts) |
target:coverage:<path> |
Force a specific coverage report path instead of auto-detection |
mode:all / no argument |
Full audit - every discovered test file and auto-detected coverage report. |
STRICT PARSING: derive target ONLY from explicit text in $ARGUMENTS. Do NOT infer from conversation context, recent blocks, or memory.
Announce: Running test-audit - scope: [FULL | target: <resolved>] - stack: <pending detection>
Step 1 - Stack detection
Detect the primary stack in this priority order. First matching marker wins.
| Stack | Marker file(s) |
|---|---|
| node-ts | tsconfig.json + package.json |
| node-js | package.json (no tsconfig.json) |
| python | pyproject.toml or requirements.txt or setup.py |
| go | go.mod |
| rust | Cargo.toml |
| swift | Package.swift or *.xcodeproj / *.xcworkspace |
| kotlin | build.gradle.kts or build.gradle with kotlin( plugin |
| dotnet | *.csproj or *.sln |
| ruby | Gemfile |
| java | pom.xml or build.gradle (no Kotlin plugin) |
| generic | None of the above |
What ships with it
2 files 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.
- 10d ago First seen · 285 lines · 64 tokens per session scan A 419728b927ae
test-audit is a skill published in the GitHub repository marcoguillermaz/Tierward (4 stars, last pushed 3d ago), licensed MIT. It adds 64 tokens to every session and 3,754 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
tdd
Discipline skill — TDD red-green-refactor cycle. Use when implementing any feature or bugfix, before writing implementation code.
qa-cycle
QA + bugfix cycle until it passes.
test-quality
Write high-quality JUnit 5 tests with AssertJ assertions. Use when user says "add tests", "write tests", "improve test coverage", or when reviewing/creating test classes for Java code.
tdd-cycle
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
genie-orca-review
Independent, read-only review of a group, a wish, or a PR on Orca — SHIP / FIX-FIRST / BLOCKED with severity-tagged findings. Council and retro are this skill with a different input.
argot-check
Score your working changes with argot — flag code foreign to this repo's own patterns (unfamiliar dependencies, APIs, constructs), functions the repo already has, code filed in the wrong place, imports that break the repo's layering, and tests weakened, disabled, or deleted alongside a production change — before…