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 agentmods add skills/smart-ai-memory/attune-ai/testingnpx skills add Smart-AI-Memory/attune-ai --skill testinggit clone --depth 1 https://github.com/Smart-AI-Memory/attune-aiWrote 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/smart-ai-memory/attune-ai/testing)<a href="https://agentmods.dev/skills/smart-ai-memory/attune-ai/testing"><img src="https://agentmods.dev/badge/skills/smart-ai-memory/attune-ai/testing.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.01060 |
| Opus 5 | $0.00005 | $0.00530 |
| Sonnet 5 | $0.00002 | $0.00212 |
| Haiku 4.5 | $0.00001 | $0.00106 |
Grade A, and why
testing 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 3d 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
testing
Test runner, generation, and coverage analysis.
Default mode: Module-level testing for daily development. Full suite reserved for release verification and deep audits.
Routes
| Subcommand | Action |
|---|---|
run |
Run tests (changed modules by default) |
quick |
Run tests for recently changed files |
coverage |
Coverage analysis (module or full) |
gen |
Generate tests |
generate |
Generate tests |
audit |
Deep coverage audit (TestAuditWorkflow) |
benchmark |
Run benchmarks |
generate --batch |
Batch test generation |
Usage
/testing # Ask what to do
/testing run # Run tests for changed modules
/testing run --all # Run full test suite
/testing quick # Run tests for changed files
/testing coverage # Module-level coverage
/testing coverage --full # Full codebase coverage
/testing audit # Deep coverage audit workflow
/testing gen # Generate tests
Fast-Path Detection
When explicit args satisfy scoping, skip questions:
/testing run --all→ full suite immediately/testing gen src/auth→ generate for that module/testing coverage --full→ full codebase coverage/testing run→ ask which tests/testing→ ask what to do
Rule: If input contains BOTH an action AND a
target (or --all/--full flag), proceed to
execution. If either is missing, use
AskUserQuestion.
Behavior
run
Default behavior: detect changed files via git diff and
run only their corresponding test files (module-level).
Use AskUserQuestion to scope if no flags provided:
- Changed modules only (default), specific directory, or full suite?
- Quick smoke test or thorough run?
# Default: changed modules only
git diff --name-only HEAD | grep '\.py$'
# Map source files to test files, then:
uv run pytest <test_files> -q
# With --all flag: full suite
uv run pytest tests/unit/ -q
# With --coverage flag: add coverage for changed modules
uv run pytest <test_files> --cov=attune.<module> -q
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.
- 3d ago First seen · 177 lines · 10 tokens per session scan A ed249284d69e
testing is a skill published in the GitHub repository Smart-AI-Memory/attune-ai (10 stars, last pushed today), licensed Apache-2.0. It adds 10 tokens to every session and 1,060 once invoked, about $0.0001 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
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
agent-wiki-ingest
Ingest one or more agent trajectories (raw bob/claude traces or normalized JSON) into an agent-wiki end-to-end — convert, summarize, extract guidelines, synthesize skills, consolidate into clusters, and catalog. Use when you have a batch of traces to turn into a wiki in one pass.
save
Captures the current session's successful workflow and saves it as a reusable skill with SKILL.md and helper scripts.
agent-wiki-tasks
Discover task families across summaries and write per-family comparison pages with findings narrative. Updates wiki-twobatch/config.yaml task definitions and writes tasks/ task.md.
evolve-lite:synthesize-skill
Convert a saved trajectory into a reusable agent skill (SKILL.md + supporting scripts) that future agents can invoke to skip rediscovered work. Use when a session captured a non-trivial workflow worth promoting from a free-text guideline to an executable skill.
learn
Must be used near the end of any non-trivial turn that produced potentially reusable tools, guidance, errors, workarounds, or workflows, so those lessons are saved for future turns.