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.
git clone --depth 1 https://github.com/brody-0125/my-claude-skillsWrote 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/plugins/brody-0125/my-claude-skills/sub-test-engineer)<a href="https://agentmods.dev/plugins/brody-0125/my-claude-skills/sub-test-engineer"><img src="https://agentmods.dev/badge/plugins/brody-0125/my-claude-skills/sub-test-engineer.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
sub-test-engineer 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 8d 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
{
"name": "sub-test-engineer",
"description": "Type-aware testing workflow agent for Java/Kotlin/TypeScript backends",
"version": "0.1.0",
"hooks": {
"PostToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "file=$(echo \"$CLAUDE_TOOL_INPUT\" | jq -r '.file_path // .path // empty' 2>/dev/null); if [ -n \"$file\" ] && echo \"$file\" | grep -qE '(Test|Spec)\\.(kt|java|ts|tsx)$'; then echo \"[Hook] Compile-checking test: $file\"; cd \"$(git rev-parse --show-toplevel 2>/dev/null || echo .)\" && if echo \"$file\" | grep -qE '\\.(kt|kts)$'; then ./gradlew compileTestKotlin --quiet 2>&1 | tail -10 || true; elif echo \"$file\" | grep -qE '\\.java$'; then ./gradlew compileTestJava --quiet 2>&1 | tail -10 || true; elif echo \"$file\" | grep -qE '\\.(ts|tsx)$'; then npx tsc --noEmit 2>&1 | tail -10 || true; fi; fi"
}
]
}
],
"Stop": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "root=$(git rev-parse --show-toplevel 2>/dev/null); if [ -n \"$root\" ]; then changed=$(git -C \"$root\" diff --name-only HEAD -- '*Test.kt' '*Test.java' '*Spec.kt' '*.test.ts' '*.spec.ts' 2>/dev/null); if [ -z \"$changed\" ]; then echo '[Hook] No test changes — skipping'; exit 0; fi; cd \"$root\" && if [ -f gradlew ]; then ./gradlew test --quiet 2>&1 | tail -5; elif [ -f package.json ]; then npm test -- --silent 2>&1 | tail -10; fi; result=$?; if [ $result -ne 0 ]; then echo 'Generated tests failed. Fix before ending.'; exit 2; fi; fi"
}
]
}
]
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 93 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 8d ago First seen · 30 lines scan A c07257ad8612
sub-test-engineer is a plugin published in the GitHub repository brody-0125/my-claude-skills (2 stars, last pushed 6mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
rot-dtd-goal
A /goal engine whose completion is EARNED, not announced. Acceptance criteria are real shell commands; the Stop hook re-runs every one of them and only exits 0 lets a goal finish. Verification defends itself: a sealed integrity ledger re-hashes each criterion before the gate trusts it, a negative-control red team…
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
polygraph
A polygraph for your state machine. The agent does the hard part for you: it instruments your code, builds any test doubles needed to run it, and captures real execution traces — then has an LLM derive a transition-function spec from the source (default: a SAM v2 strict-profile module with named…
workinggenius
A development workflow that walks every piece of work through the six Working Geniuses — Wonder, Invention, Discernment, Galvanizing, Enablement, Tenacity — every stage a command the user types, every checkpoint a live exchange.
dev-loop
loop-orchestrator's verification loop (TDD / PDCA / Reflexion) with the plan step FIXED to a wiki-grounded planning methodology (wiki-plan): every design decision is routed to a bundled semantic-layer wiki before code is written. Adds a knowledge-capture loop — sessions emit verified insights, and knowledge-flush…
harnessay
Profile your Claude Code transcripts: context budget report, skill-promotion candidates, and a skill regression test harness. Local-only, stdlib-only.