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 skills add brcampidelli/chimera-agent --skill chimera-test-the-wiring-not-the-classgit clone --depth 1 https://github.com/brcampidelli/chimera-agentWrote 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/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class)<a href="https://agentmods.dev/skills/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class/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/skills/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01237 |
| Opus 5 | $0.00018 | $0.00619 |
| Sonnet 5 | $0.00007 | $0.00247 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
chimera-test-the-wiring-not-the-class 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 12d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger
You built a component that production reaches indirectly: through a factory, a registry, a plugin loader, a config flag, a router, a CLI entrypoint, a dependency-injection container. Your tests construct it directly and call its methods.
Every one of those tests can pass while the component is unreachable in the running system — because nothing in them exercises the registration, the default value of the flag, or the branch in the assembler that decides whether to include it at all.
It does not apply to a pure function that callers import and call directly. There, the import is the wiring, and a unit test covers it. It also does not apply when you are deliberately testing an algorithm in isolation — those tests are correct and should stay; this card says they are not sufficient on their own.
Do
-
Name the entrypoint a user actually hits: the CLI subcommand, the HTTP route, the agent's run loop, the scheduled job. Write it down before writing the test.
-
Write at least one test that starts there and passes no constructor arguments for your component. If the test has to name your class to make the feature happen, it is not testing the wiring.
-
Build the object the way production builds it — call the real factory or config loader:
# WRONG — proves the class, not the wiring: the component is handed to the thing under test, # so the test passes whether or not anything in production ever hands it over. assert "reminder" in render(feature=Feature(text="reminder")) # RIGHT — build it the way the entry point builds it, then look for the same observable assert "reminder" in build_the_real_way(config).render()Chimera's own case is worth naming because the class was never broken. Skill cards had a working retriever, a working store and a working injector — and
chimera/config.py:244readsskill_cards: bool = Field(default=False, ...), so on a stock deployment nothing was ever injected. Every unit test passed. The measurement that eventually caught it counted skills minted against skills injected and found 39 against zero.
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.
- 12d ago First seen · 110 lines · 36 tokens per session scan A 564f2b0aaff3
chimera-test-the-wiring-not-the-class is a skill published in the GitHub repository brcampidelli/chimera-agent (25 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 1,237 once invoked, about $0.0002 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-30.
Other skills, from other repositories
verify-changes
Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).
iterative-refinement
Disciplined, measurable iteration for a substantial refinement or investigation: loop against verifiable pass/fail conditions, fan work out to subagents, and keep the main context lean. Use when improving something measurable over repeated cycles (tuning a metric or detector, refactoring against a regression bar)…
ap-policies
Attach a completion policy gate (shell check or judge-agent rubric) to a session or fan-in group so turn-end only passes when the gate is green, then optionally auto-commit pending human ack. Use when the user says "gate this session on tests passing", "attach a policy", "commit only if tests are green", "judge…
GitHub Issues
Triage GitHub issues, extract the real ask, and connect each issue to the relevant files, tests, or release surface before acting.
Test Driven Development
Drive behavior changes through a failing test, the smallest working implementation, and then cleanup once the behavior is locked.