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 hereinthehive/gotrino-assistant --skill examples-auditgit clone --depth 1 https://github.com/hereinthehive/gotrino-assistantWrote 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/hereinthehive/gotrino-assistant/examples-audit)<a href="https://agentmods.dev/skills/hereinthehive/gotrino-assistant/examples-audit"><img src="https://agentmods.dev/badge/skills/hereinthehive/gotrino-assistant/examples-audit.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.00036 | $0.01129 |
| Opus 5 | $0.00018 | $0.00564 |
| Sonnet 5 | $0.00007 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
examples-audit 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 8d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Examples Audit
Analyze mock data and examples for cultural assumptions, with emphasis on understanding what these choices communicate.
Philosophy
This is not about finding "Christmas" and replacing it with "holiday". It's about asking:
"What do our examples say about who we think our users are?"
Every example is a choice. When your demo shows a user ordering a hamburger for their Christmas party, paying with a credit card, and shipping to their house in California, you're painting a picture of your "default user." Everyone else is an edge case.
Scope
The user may specify a file path, glob pattern, or directory. If not specified, ask what they'd like to check.
Config Integration
Before starting, follow the migration preflight in references/config-migration.md, then read .assistant-config.md from the project root.
If it exists:
- Read scope decisions and acknowledged findings
- Skip acknowledged findings (note them in output)
- Respect scope decisions (e.g., if US-only, don't flag US address examples)
- Note at the top of output: "Config loaded: .assistant-config.md"
Process
1. Read and Understand
First, read the content to understand:
- What is this? (test data, documentation, marketing, UI copy)
- Who sees this? (developers only, or end users?)
- What story are the examples telling?
2. Look for Patterns
Don't just flag individual terms. Look for patterns:
- Do ALL the examples assume US location?
- Do ALL the food references assume meat-eating?
- Do ALL the family references assume nuclear families?
- Do ALL the payment examples assume credit cards?
A single Christmas reference in otherwise diverse examples is different from a codebase where every example assumes Christian, Western, affluent users.
3. Understand the Assumptions
For each pattern, ask what it assumes:
Holiday/Event examples
- Christmas, Easter, Thanksgiving → Assumes Christian/Western holidays
- "Holiday season" in December → Assumes Northern hemisphere
- Birthday celebrations → Not all cultures celebrate birthdays
- Mother's Day, Father's Day → Can be painful; not universal
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.
- 8d ago First seen · 168 lines · 36 tokens per session scan A 492add143fc9
examples-audit is a skill published in the GitHub repository hereinthehive/gotrino-assistant (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 1,129 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-31.
Other skills, from other repositories
magpie-pr-management-quick-merge
Identify trivial, low-risk pull requests in the ready for maintainer review queue of that pass every quality gate and touch only supplementary areas (docs, changelog, translations, tests) — the "express lane" a maintainer can review and merge in seconds. Surfaces and ranks candidates with per-PR diff summaries, an…
review-all
Multi-agent code review for diffs (project-agnostic). Covers standards, bugs, security, DRY, smells, perf, tests, API contracts, a11y/i18n. Verifies each finding to eliminate false positives. Use for /review-all, pre-PR/pre-commit review, or auditing uncommitted/staged changes.
fec-drawio-studio
An editable workflow for making technical diagrams in draw.io (also called diagrams.net), with the original .drawio file saved alongside exported images or documents. It covers architecture, database, UML, sequence, flow, machine-learning, and code-structure diagrams.
fec-nextjs-project-standard
A development guide for Next.js 14 and newer projects using App Router, Next.js’s file-based routing system. It covers server-rendered pages, layouts, data loading, middleware, metadata, and server actions.
fec-monorepo-project-standard
A guide for organising a monorepo, which is one code repository containing several applications and shared packages. It covers workspace dependencies, folder structure, build tasks, testing, caching, and package releases.
fec-route-protection
A guide for protecting front-end routes, meaning the pages and URLs of a web application, based on whether someone is signed in and what permissions they have. It covers login checks, role-based access, expired sessions, and redirects.