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 inclusion-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/inclusion-audit)<a href="https://agentmods.dev/skills/hereinthehive/gotrino-assistant/inclusion-audit"><img src="https://agentmods.dev/badge/skills/hereinthehive/gotrino-assistant/inclusion-audit/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/hereinthehive/gotrino-assistant/inclusion-audit"><img src="https://agentmods.dev/badge/skills/hereinthehive/gotrino-assistant/inclusion-audit.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.00034 | $0.01658 |
| Opus 5 | $0.00017 | $0.00829 |
| Sonnet 5 | $0.00007 | $0.00332 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
inclusion-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 11d 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inclusion Audit
Comprehensive inclusion analysis that examines code through the lens of who it serves and who it might exclude.
Philosophy
This is not a checklist to pass. It's a way of seeing:
"Every line of code makes assumptions about who will use it. What are ours?"
The goal isn't to find problems—it's to understand your code from the perspective of users who aren't like you. Users in different countries. Users with different abilities. Users with different family structures, beliefs, and circumstances.
Note: This is a thorough review. For quick checks, use the focused skills: /language-check, /i18n-check, /names-check, /examples-audit.
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, priorities, and acknowledged findings
- Skip sections that are out of scope (e.g., skip i18n section if US-only)
- Skip acknowledged findings (note count in output)
- Respect priorities when ordering recommendations
- Note at the top of output:
**Config loaded:** .assistant-config.md **Skipped:** i18n (out of scope), 3 acknowledged findings
Core dignity checks (slurs, hostile language) always run regardless of config.
Process
1. Understand the Context
Before analyzing, understand:
- What does this code do? Who uses it?
- What's the target audience? (Global? Specific regions? Enterprise? Consumer?)
- What's the visibility? (Internal tool? Public-facing app?)
This shapes what matters most.
2. The Core Question
Throughout your analysis, keep asking:
"What am I assuming about the person using this?"
Every assumption is a potential exclusion.
3. Analysis Areas
Language
Read the code, comments, documentation, and UI text. Look for:
- Language that assumes gender, ability, or identity
- Terms with harmful history or associations
- Tone that might make some users feel unwelcome
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.
- 11d ago First seen · 224 lines · 34 tokens per session scan A 6de5dbd0e42f
inclusion-audit is a skill published in the GitHub repository hereinthehive/gotrino-assistant (5 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 1,658 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-component-testing
A guide for writing and reviewing front-end unit, component, and lightweight integration tests. These tests check small pieces of code and UI behavior without running a full browser journey.
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.