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 tienenwu/fables --skill golden-examplesgit clone --depth 1 https://github.com/tienenwu/fablesWrote 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/tienenwu/fables/golden-examples)<a href="https://agentmods.dev/skills/tienenwu/fables/golden-examples"><img src="https://agentmods.dev/badge/skills/tienenwu/fables/golden-examples.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.1 | $0.00060 | $0.00969 |
| Opus 5 | $0.00030 | $0.00485 |
| Sonnet 5 | $0.00012 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
golden-examples 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🌐 繁體中文（canonical） · English mirror
Golden examples (golden-examples) — skeleton
This is the skeleton version. A golden-examples library's whole value is "your own real adjudications" — someone else's samples can't set your tone — so this file keeps only the mechanism (usage, intake rules, format) and leaves the content of §1–4 blank for you to fill.
Usage: before you write, read the matching section and imitate the shape of the "after." Every example carries a judgment point — the part a rule can't state, that you can only absorb from an example. The "before" should come from real history, not a straw man.
Every example below is a
<placeholder>, marked "(illustrative — replace)". Replace them with adjudications you receive in real tasks — before your first intake, delete that section's illustrative example.
1. Commit message
One line: the reader of a commit message is "the person running git blame three months from now"; verb + object + purpose is what makes it searchable.
Format illustration (replace)
- Before:
<the original commit message the user rejected, e.g. "update code"> - After:
<the version the user approved, e.g. "refactor: normalize module X's verbose comments to one style"> - Judgment point:
<the principle from this adjudication that transfers to next time — one sentence>
2. UI copy (this skill's primary scenario is Japanese copy — see frontmatter)
One line: UI text must fit the target language's native idiom; error messages are two-part (what happened + what the user can do), and the error code goes to the log, not the screen.
Format illustration (replace)
- Before:
<the original string that reads machine-translated or colloquial> - After:
<the idiomatic version the user changed it to> - Judgment point:
<transferable principle, e.g. "labels use noun + verb; avoid katakana transliteration">
3. Code review comments
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 · 63 lines · 60 tokens per session scan A ff24f6590f85
golden-examples is a skill published in the GitHub repository tienenwu/fables (4 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 969 once invoked, about $0.0003 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
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…