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.03758 |
| Opus 5.5 | $0.00026 | $0.01503 |
| Sonnet 5.5 | $0.00013 | $0.00752 |
| Haiku 4.5 | $0.00006 | $0.00376 |
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 14d 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 — 286 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.
- 14d ago Changed · +1 lines 1cbb2c238904
- 1mo 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 today), licensed MIT. It adds 64 tokens to every session and 3,758 once invoked, about $0.0003 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
github-issue-to-pr
Implement one scafld-governed repository issue with normal host tools, prove the tested change through its finalize wall, and optionally publish the exact pull request through scoped provider authority with readback.
schema-check
Check a proposed API or data contract against the current contract, real sample payloads, and a compatibility policy, and gate publication behind a refusable verdict with native digest evidence.
writing-playwright-tests
Provides patterns for writing maintainable E2E test scripts with Playwright, focusing on selector strategies, page objects, and wait handling for legacy application retrofitting.
smoke-test-database
Quick Reference - Load this first for fast context (3KB).
ensemble-implement-trd
Complete TRD implementation using git-town workflow with ensemble-orchestrator delegation and TDD methodology (Codex skill for /ensemble:implement-trd).
ensemble-validate-requirements
Pre-implementation traceability gate — validates REQ-NNN coverage and TEST task pairing between PRD and TRD (Codex skill for /ensemble:validate-requirements).