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/cintia09/codenook/test-runnernpx skills add cintia09/CodeNook --skill test-runnergit clone --depth 1 https://github.com/cintia09/CodeNookWhat 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.00003 | $0.01329 |
| Opus 5 | $0.00002 | $0.00665 |
| Sonnet 5 | $0.00001 | $0.00266 |
| Haiku 4.5 | $0.00000 | $0.00133 |
Grade A, and why
test-runner scanned grade A with 1 finding 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 2d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
`subprocess.run(..., shell=True)` inside the target directory. The How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
test-runner — plugin-shipped skill (development plugin)
Role
Wrap the workspace's actual test runner (pytest / jest / go test) so the tester role can issue a single command and parse a single exit code.
CLI
runner.py --target-dir <dir> [--config <path>] [--json]
--config is optional; when supplied, it overrides the marker
detection and runs whatever command the config file defines (see
Memory-first lookup, below).
Three-tier resolution (memory-first, ask-second)
Security / threat model
--config <path> is executed as a Python module (via
runpy.run_path); the module-level TEST_CMD is then executed via
subprocess.run(..., shell=True) inside the target directory. The
Python execution gives the config full host privileges (it can import os; os.system(...) etc.) before any test even starts. This is
intentional — the memory-first pattern needs full flexibility to wrap
arbitrary test runners (pytest selectors, custom wrappers, env-var
preludes, SSH-into-DUT, etc.). Consequences:
- The caller is responsible for trust. Only point
--configat: (a) a workspace-memory entry under.codenook/memory/knowledge/that a human author wrote / reviewed; OR (b) a snippet just pasted by the current user via HITL. - Never load a
--configfile fetched over the network without human review first. - The skill makes no attempt to sandbox the config or the test
runner — anything Python (and
shell=True) can do, the config can do. - Memory entries shipped by plugins (under
.codenook/plugins/<id>/) are not auto-trusted; they reach--configonly after a human promotes the embedded snippet to a memory file.
This skill is environment-agnostic: it does not know about ADB, QEMU, SSH-into-board, JTAG, etc. Instead, it follows a three-tier resolution that lets the workspace's memory describe the target, with the user as the ultimate fallback:
- Marker detection inside
<target-dir>(legacy v0.3 behaviour). If the directory containspyproject.toml/setup.py/pytest.ini/tox.ini→ runpytest.package.json→npm test.go.mod→go test ./.... This is the fast path for pure-software targets.
What ships with it
1 file 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.
- 2d ago First seen · 131 lines · 3 tokens per session scan A 476f3f7c5202
test-runner is a skill published in the GitHub repository cintia09/CodeNook (5 stars, last pushed 3mo ago), licensed MIT. It adds 3 tokens to every session and 1,329 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
create-skill
Create new Datus skills from scratch. Use when users want to build a new skill, scaffold a skill directory, or capture a workflow as a reusable skill. Trigger phrases include "create a skill", "make a skill for", "turn this into a skill", "new skill".
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
convex-insights
Query a running Convex app's logs + health in natural language (official MCP): failures, slow/expensive functions, deploy causality — scoped, evidence-backed, with a dashboard deep link.
openclaw-design-system
Compatibility alias for existing OpenClaw installations that now applies Carapace semantic tokens, themes, shared CSS foundations, consumer adapters, and established local primitives.