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 arunveersingh/ai --skill day-16-golden-bitegit clone --depth 1 https://github.com/arunveersingh/aiWrote 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/arunveersingh/ai/day-16-golden-bite)<a href="https://agentmods.dev/skills/arunveersingh/ai/day-16-golden-bite"><img src="https://agentmods.dev/badge/skills/arunveersingh/ai/day-16-golden-bite/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/arunveersingh/ai/day-16-golden-bite"><img src="https://agentmods.dev/badge/skills/arunveersingh/ai/day-16-golden-bite.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00107 | $0.01065 |
| Opus 5.5 | $0.00043 | $0.00426 |
| Sonnet 5.5 | $0.00021 | $0.00213 |
| Haiku 4.5 | $0.00011 | $0.00106 |
Grade A, and why
golden-bite 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 7d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golden bite
An AI step matches incoming bank transfers to open invoices, or returns UNMATCHED for a person. The golden set has 240 cases written at launch (71 of them agent-written rewordings), and the feared harm (a payment booked to another customer's invoice) has its own zero-miss line. Prompt v7 adds "if the remittance contains an open invoice number, match it". It scores 240/240 and ships. Nine business days later, 37 payments are on the wrong customer: "PO 10452" was the payer's own purchase order, and INV-10452 belonged to someone else. Replayed on v7, the golden set still scores 240/240. In every case the invoice number, payer and amount agreed, so any version got them right.
Covered is not caught. Prove a case can fail before you trust it to pass.
Part A — Ask (project rules, or paste after a bug ticket for an AI step)
When you fix a mistake an AI step made:
1. MISTAKE: the real input, exactly as it came in, and what the step did with it.
2. CASE: add it to the golden set with expected left blank. I'll get it from the owner.
3. BITE: run the new case on the version that made the mistake. It must fail.
If it passes, say TOOTHLESS and rewrite it from the real input.
4. Only then change the prompt or model. Report: new cases | fail on old | pass on new.
Never edit an expected label. If one looks wrong, reply:
LABEL DISPUTE | case | why, and stop.
In an orchestrated flow (spec → plan → tasks → implement): name who labels each AI step's golden cases in the spec; when a task fixes an AI mistake, its first step adds the mistake as a case and shows it failing on the current version; each task review shows the bite count and any label changes with the owner's name.
Part B — Check (you do this)
bite_check.py has no dependencies. It reads a golden file (id,source,labelled_by,expected) plus results files (id,predicted) from one or more known-bad versions and a candidate. It counts, per source, how many cases fail on a known-bad version (their teeth) and how many the candidate passes. Cases labelled by the agent, or by nobody, aren't counted. Replay the story on made-up files:
What ships with it
2 files 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.
- 7d ago First seen · 57 lines · 107 tokens per session scan A 8a8cca2f7a4d
golden-bite is a skill published in the GitHub repository arunveersingh/ai (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 107 tokens to every session and 1,065 once invoked, about $0.0004 per session on Opus 5.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-10-18.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.