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/jxoesneon/ciel/test_runnernpx skills add jxoesneon/Ciel --skill test_runnergit clone --depth 1 https://github.com/jxoesneon/CielWrote 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/jxoesneon/ciel/test_runner)<a href="https://agentmods.dev/skills/jxoesneon/ciel/test_runner"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/test_runner.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.00016 | $0.00336 |
| Opus 5 | $0.00008 | $0.00168 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
test_runner 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 5d 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_runner
Execute and analyze tests.
Operations
test.run(target?, filter?)— run tests; returns pass/fail/error counts + failure details.test.coverage(target?)— coverage report with file-level breakdown.test.diagnose(failure)— suggest root cause from stack trace + recent diffs.test.rerun(strategy)— retry-only-failing, full, or bisect-over-commits.
I/O Contract
io_contract:
input: { op, "target?", "filter?", "coverage?" }
output: { summary: { passed, failed, skipped }, failures: [ { name, trace } ], "coverage?" }
idempotent: partial
side_effects: [shell, fs]
Framework Detection
Auto-detects pytest, jest, mocha, cargo test, go test, rspec, phpunit, dotnet test, JUnit, etc. Respects project test config.
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.
- 5d ago First seen · 37 lines · 16 tokens per session scan A 50abf0eada20
test_runner is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 16 tokens to every session and 336 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
redpolicy-guide
Ред-политика для гайдов по вебинарам. Превращаем транскрибации вебинаров в структурированные самостоятельные тексты. Две части: быстрый старт + подробный разбор.
Code Quality Review
Conduct a comprehensive code quality review focused on clean code, architecture, and project standards.
write-overview
Полный цикл создания обзорной статьи-эссе по теме проекта.
redpolicy-article
Ред-политика для статей-подборок сервисов. Пишем обзоры сервисов, инструментов и продуктов для аудитории проекта. Каждый сервис описывается по шаблону: название, ссылка, стоимость, описание.
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
boil-ocean
Use when the user hands over a big multi-sprint task to finish end-to-end without supervision — "build the whole spec", "implement it all", "do all the sprints", "boil the ocean", "take the decisions yourself", "don't stop until it's done" — or when resuming an existing run (.ocean/state.json exists in the repo, or…