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 kunalsuri/ai-fication-kit --skill deep-testgit clone --depth 1 https://github.com/kunalsuri/ai-fication-kitWrote 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/kunalsuri/ai-fication-kit/deep-test)<a href="https://agentmods.dev/skills/kunalsuri/ai-fication-kit/deep-test"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/deep-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/kunalsuri/ai-fication-kit/deep-test"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/deep-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.00049 | $0.00394 |
| Opus 5.5 | $0.00020 | $0.00158 |
| Sonnet 5.5 | $0.00010 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
deep-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.
What it actually says
Deep test the codebase
This skill performs a thorough and strict verification of the codebase to guarantee that changes are clean, functional, matches Conventions, contains proper license headers, and does not leak template placeholders.
1. Prerequisites
Ensure you have the required runtimes and node dependencies installed:
- Node.js (>= 18)
- Run
npm installbefore running tests if dependencies are updated.
2. Run the Deep Test
Run the automated deep test script via npm:
npm run deep-test
3. Verify Output
The script automatically tests:
- Smoke tests:
node test/run-tests.mjs - Document Claim verification:
node install.mjs verify . --strict - Structural Drift verification:
node install.mjs drift . --strict --git(falls back to--strictwithout--gitif git is not available) - License Headers check: Scans files for copyright markers.
- Unresolved template placeholders: Confirms template variables are not leaked outside of
templates/.
If any of the checks fail, print the failures verbatim and address them before declaring success.
4. Manual Verification / Check Checklist
- If you introduced new files, check that their paths are added to the appropriate catalog or map (e.g.,
ai/guide/MODULE_MAP.md) and labeled as[inferred]. - Verify the change adheres to all project rules in
AGENTS.mdand conventions inai/guide/CONVENTIONS.md.
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 · 35 lines · 49 tokens per session scan A 542a14df34b1
deep-test is a skill published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 10d ago), licensed Apache-2.0. It adds 49 tokens to every session and 394 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
mantis-configure
Configures and validates Mantis pipeline environments, sandbox mechanisms, and AI models. Use to set up workflow.json, auto-detect host capabilities, switch between sandboxes (static-only, gvisor, microsandbox, gce), select AI models, and run fast 1-2s preflight tests. Don't use for scanning source code or running…
09-for-sure
Run an iterative agent loop that retries until a runnable success condition passes. Use when the user says "for sure", "keep trying until", or wants guaranteed completion against a success command. Not for one-shot tasks or uncheckable goals.
verify
Run x-harness read-only verification.
execute
Implements a plan step by step, verifies named tests or explicit manual scenarios, enforces the product-behavior guardrail and five-attempt retry limit, and completes with the plan's automated regression gate or validated manual evidence. Use when executing a plan that plan-the-work already wrote.
define-test-strategy
Onboards or refreshes a repo's test-strategy skill and shared test map: discovers tests across repos without modifying source/tests, discusses layers and adoption, records commands and prerequisites, maintains evidence-backed UC/domain relationships, and reports coverage.
run-regression
Runs a project's regression suite — full, per repo (full: ), or scoped to repo-qualified use-case/domain tokens across every test location — and reports pass/fail results; the shared implementation execute calls at the end of a plan. Use when running or checking a project's test suite, full or scoped to specific…