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 agentmods add skills/hereinthehive/gotrino-assistant/plugin-helpnpx skills add hereinthehive/gotrino-assistant --skill plugin-helpgit 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/plugin-help)<a href="https://agentmods.dev/skills/hereinthehive/gotrino-assistant/plugin-help"><img src="https://agentmods.dev/badge/skills/hereinthehive/gotrino-assistant/plugin-help.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 | $0.00017 | $0.00847 |
| Opus 5 | $0.00009 | $0.00424 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
plugin-help 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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plugin Help
Show available commands and explain how to use the Gotrino assistant.
Output
# Gotrino Assistant
A development assistant with skills for inclusion, triage, impact analysis, and more.
## Quick Reference
### Fast Checks (run anytime)
| Command | What it does |
|---------|--------------|
| `/guardian [path]` | Quick inclusion gut-check (lightweight) |
| `/language-check [path]` | Scan for non-inclusive language |
| `/names-check [path]` | Check name diversity in examples |
| `/i18n-check [path]` | Find internationalization issues |
### Deeper Analysis
| Command | What it does |
|---------|--------------|
| `/examples-audit [path]` | Analyze mock data for cultural assumptions |
| `/inclusion-audit [path]` | Comprehensive inclusion review |
| `/test-assumption [path]` | Identify hidden assumptions about users |
### Debt Analysis
| Command | What it does |
|---------|--------------|
| `/code-debt [path]` | TODO markers, dead code, deprecated APIs, oversized units |
| `/doc-debt [path]` | Stale docs, missing API docs, broken links, undocumented env vars |
| `/test-debt [path]` | Skipped tests, untested public APIs, flaky patterns |
| `/dep-debt` | Outdated, unused, or abandoned dependencies |
| `/design-debt [path]` | Inconsistent patterns, architectural drift, duplicated logic |
| `/debt-audit [path]` | Run all debt dimensions, synthesize cross-cutting findings |
### Utilities
| Command | What it does |
|---------|--------------|
| `/inclusive-names` | Generate diverse name suggestions |
| `/explain [path]` | Create decision record in `decisions/` |
| `/impact [path]` | Analyze change impact before making it |
| `/triage` | Triage an incoming request, draft a ready-to-file issue |
### Setup
| Command | What it does |
|---------|--------------|
| `/teach-charter` | Configure plugin for your project |
## Typical Workflow
**Starting a new project:**
1. Run `/teach-charter` to set up your `.assistant-config.md`
2. Define your scope (US-only? Global? etc.)
3. Set priorities for your team
**During development:**
- Run `/guardian` after generating forms, UI, or examples
- Chain it: "create the signup form, then /guardian it"
- Run focused checks (`/language-check`, `/names-check`) as needed
**Before shipping:**
- Run `/inclusion-audit` for comprehensive review
- Run `/test-assumption` on user-facing flows
## Configuration
Your settings are stored in `.assistant-config.md`:
- **Scope decisions**: What's in/out of scope (e.g., i18n for US-only products)
- **Acknowledged findings**: Issues you've reviewed and accepted
- **Priorities**: What matters most for your project
- **Decisions location**: Where `/explain` saves decision records (default: `decisions/`)
Run `/teach-charter` to create or update this file.
## Philosophy
This assistant isn't a linter. It's a **second pair of eyes** that asks:
> "Who might this exclude? What assumptions are baked in?"
It won't catch everything, and not everything it catches needs fixing. Use judgment. The goal is code that welcomes more users, not compliance with rules.
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.
- 4d ago First seen · 100 lines · 17 tokens per session scan A a6273ebf9ce6
plugin-help is a skill published in the GitHub repository hereinthehive/gotrino-assistant (5 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 847 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…