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-give-the-denominatorgit 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-give-the-denominator)<a href="https://agentmods.dev/skills/brcampidelli/chimera-agent/chimera-give-the-denominator"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-give-the-denominator/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-give-the-denominator"><img src="https://agentmods.dev/badge/skills/brcampidelli/chimera-agent/chimera-give-the-denominator.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.00040 | $0.01021 |
| Opus 5 | $0.00020 | $0.00511 |
| Sonnet 5 | $0.00008 | $0.00204 |
| Haiku 4.5 | $0.00004 | $0.00102 |
Grade A, and why
chimera-give-the-denominator 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trigger
You are about to put a rate, a percentage, or a count into a report, a commit message, a benchmark table, or a message to someone who will act on it. "34% of runs failed." "Errors up 3x." "Coverage dropped."
It does not apply to a number the reader can already decompose: a single measured latency, a version string, a count of files in a diff they can see. The risk is specific to an aggregate — a quantity computed by dividing one set you chose by another set you chose, where both choices are invisible in the sentence.
Do
- Write the raw counts next to the rate, always:
34% (17/50 runs). If you cannot state the denominator, you do not yet know what you measured. - Say which denominator. Attempted runs and completed runs are different sets, and dividing by completed silently deletes the crashes — the exact population that made you look.
- Split the numerator by cause before publishing it. Of those 17 failures, how many are an
already-open issue, a known flaky provider timeout, a fixture that fails on this machine?
Report the split:
17 failed — 14 are the known connect timeout, 3 unexplained. - Run the same measurement against an unchanged baseline and subtract. The number that matters
is the part that does not survive on
main. - When n is small enough that one more sample would move the headline figure by several points, put that sentence in the report instead of the percentage.
Avoid
"failure rate 34%" — true, and it invites the reader to spend a day on a timeout they already
filed last week. Write "17/50 failed; 14 are the ollama connect timeout (issue open), 3 are new"
and the day gets spent on the 3.
Avoid the survivorship denominator. rate = failures / completed is the classic: the runs that
died before producing a row are absent from both sides, so the metric improves as the system gets
worse.
Avoid percentages over a denominator under about twenty without n attached. 50% → 67% is a real
improvement or it is one run out of three flipping, and the two are indistinguishable on the page.
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 · 88 lines · 40 tokens per session scan A a95d8e10515e
chimera-give-the-denominator is a skill published in the GitHub repository brcampidelli/chimera-agent (25 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 1,021 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
agentscope-java
Expert Java developer skill for AgentScope Java framework - a reactive, message-driven multi-agent system built on Project Reactor. Use when working with reactive programming, LLM integration, agent orchestration, multi-agent systems, or when the user mentions AgentScope, ReActAgent, Mono/Flux, Project Reactor, or…
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
synthesize-report
Produces a citation-grounded summary across one or more workspace source files for summaries, briefings, literature reviews, or comparisons.
data-analysis
Statistical data analysis skill — use when the user asks to analyze numbers, compute statistics, or summarize datasets.
weknora-shared
Use when driving a WeKnora RAG server through the weknora CLI as an agent — authenticating, managing knowledge bases / documents / sessions / agents, running search or chat, or interpreting the CLI's JSON envelopes and exit codes. Read this before any other weknora- skill.
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).