chimera-test-the-wiring-not-the-class

chimera-test-the-wiring-not-the-class is a skill for Claude Code, Codex from brcampidelli/chimera-agent. It costs 36 tokens per session (1,237 once invoked), scanned A, original, Apache-2.0.

A testing practice for checking that a component is reachable through the same factory, registry, route, command, or configuration path that production uses.

In plain words
What is it for?
Use it for features reached through routers, plugin loaders, dependency-injection systems, configuration flags, CLIs, scheduled jobs, or similar wiring. Direct unit tests can remain for isolated algorithms but are not enough by themselves.
Why use it?
Directly constructing a class only proves that class works; it can still be missing from the running application. Testing the real entry point reveals broken registration or assembly.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it for features reached through routers, plugin loaders, dependency-injection systems, configuration flags, CLIs, scheduled jobs, or similar wiring. Direct unit tests can remain for isolated algorithms but are not enough by themselves.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class
Install

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.

Any agent
npx skills add brcampidelli/chimera-agent --skill chimera-test-the-wiring-not-the-class
Clone the repo
git clone --depth 1 https://github.com/brcampidelli/chimera-agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for chimera-test-the-wiring-not-the-class

README.md
[![agentmods](https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class/github.svg)](https://agentmods.dev/skills/brcampidelli/chimera-agent/chimera-test-the-wiring-not-the-class)
Your own site
<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.

agentmods 80×15 button for chimera-test-the-wiring-not-the-class

Your own site · 80×15
<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>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,237 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 12d ago against content hash 564f2b0aaff3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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.

skills/chimera-test-the-wiring-not-the-class/SKILL.md · 110 lines

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

  1. 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.

  2. 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.

  3. 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:244 reads skill_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.

Read the full file on GitHub · 110 lines

Changes

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.

  1. 12d ago First seen · 110 lines · 36 tokens per session scan A 564f2b0aaff3

Subscribe to this mod's changes

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.