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/arnwaldn/project-architectnpx agentmods add commands/arnwaldn/project-architect/test-pluginWrote 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/commands/arnwaldn/project-architect/test-plugin)<a href="https://agentmods.dev/commands/arnwaldn/project-architect/test-plugin"><img src="https://agentmods.dev/badge/commands/arnwaldn/project-architect/test-plugin/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/commands/arnwaldn/project-architect/test-plugin"><img src="https://agentmods.dev/badge/commands/arnwaldn/project-architect/test-plugin.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.00028 | $0.00203 |
| Opus 5.5 | $0.00011 | $0.00081 |
| Sonnet 5.5 | $0.00006 | $0.00041 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
test-plugin 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
Test Plugin
Execute the full integration test suite and report results.
Instructions
- Run the test suite from the repository root:
python tools/test-all.py
The script resolves its own paths, so it can also be run from anywhere:
python /path/to/project-architect/tools/test-all.py
- Report the results:
- Show the full output (10 tests)
- Highlight any FAIL or ERROR
- T9 and T10 check a local Claude Code installation. On a fresh clone they report SKIP -- that is expected, not a failure.
- If every non-skipped test passes, confirm with ALL TESTS PASSED
- If any fail, list the specific errors and suggest fixes
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 · 32 lines · 28 tokens per session scan A 0e15f209dfd5
test-plugin is a command published in the GitHub repository arnwaldn/project-architect (1 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 203 once invoked, about $0.0001 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 commands, from other repositories
sdlc-test
Phase 4 — Testing & Security. Spawns qa-manual-tester, automation-qa-engineer, appsec-engineer, penetration-tester, performance-engineer.
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
test-audit
Use when writing, reviewing, or pruning tests. Three modes, one value bar: a four-question gate before any new test is written, a focused audit of one scope, and a campaign over a whole repo or subsystem that removes the least useful tests under a coverage guard. Every delete, merge, or repair carries written evidence…