Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Destynova2/cli-code-skillsnpx agentmods add skills/destynova2/cli-code-skills/cli-audit-testWrote 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/destynova2/cli-code-skills/cli-audit-test)<a href="https://agentmods.dev/skills/destynova2/cli-code-skills/cli-audit-test"><img src="https://agentmods.dev/badge/skills/destynova2/cli-code-skills/cli-audit-test/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/destynova2/cli-code-skills/cli-audit-test"><img src="https://agentmods.dev/badge/skills/destynova2/cli-code-skills/cli-audit-test.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.00094 | $0.02624 |
| Opus 5.5 | $0.00038 | $0.01050 |
| Sonnet 5.5 | $0.00019 | $0.00525 |
| Haiku 4.5 | $0.00009 | $0.00262 |
Grade A, and why
cli-audit-test 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.
This is a copy
88% identical to api-audit — 693 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Optimization: This skill uses on-demand loading. Heavy content lives in
references/and is loaded only when needed.
Language rule: Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the report in that language. If the project is bilingual, ask the user which language to use before proceeding.
Audit Test — Test Plan Quality & Maturity Scorer
Evaluate a test plan or test suite against ISTQB standards, TMMi maturity model, and industry best practices.
"A test plan that only says 'we will test' without specifying which techniques and why is a major red flag." — ISTQB Foundation Level Syllabus v4.0
Core Principle
A test plan is a contract with quality. Every dimension left vague is a risk accepted silently. This skill measures how explicitly and completely that contract is defined, using a 12-dimension framework calibrated on ISTQB, TMMi, and proven industry patterns.
Input
$ARGUMENTS is the target to audit:
- Test plan document (
.md,.txt,.adoc,.pdf): audit the plan as written - Tests directory (
tests/,tests/e2e/, etc.): infer the plan from the test structure, files, and config - Empty: search for test plans in the project root, then fall back to
tests/directory analysis
Input Discovery
- Glob for test plan documents:
**/test-plan*,**/test-strategy*,**/TESTING* - Glob for test directories:
**/tests/**,**/test/**,**/e2e/**,**/spec/** - Glob for CI config:
.github/workflows/*,.gitlab-ci.yml,Jenkinsfile,justfile - Glob for test config:
**/pict/**,**/fixtures/**,**/mocks/**,**/toxiproxy* - Read project manifest (Cargo.toml, package.json, etc.) for test dependencies
13-Dimension Framework
Score each dimension 0-4, then compute a weighted final score. Read references/dimensions.md for detailed scoring criteria, evidence patterns, and per-dimension guidance.
What ships with it
4 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.
- 1mo ago First seen · 203 lines · 94 tokens per session scan A ab52aec1a43d
cli-audit-test is a skill published in the GitHub repository Destynova2/cli-code-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 94 tokens to every session and 2,624 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to api-audit, differing in 693 lines, and is treated as a copy.
Other skills, from other repositories
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…
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.
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).
smoke-test-database
Quick Reference - Load this first for fast context (3KB).
smoke-test-external-services
Quick Reference - Load this first for fast context (3KB).