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 gtapps/hermitd --skill domain-brainstormgit clone --depth 1 https://github.com/gtapps/hermitdWrote 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/gtapps/hermitd/domain-brainstorm)<a href="https://agentmods.dev/skills/gtapps/hermitd/domain-brainstorm"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/domain-brainstorm/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/gtapps/hermitd/domain-brainstorm"><img src="https://agentmods.dev/badge/skills/gtapps/hermitd/domain-brainstorm.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.00000 | $0.01265 |
| Opus 5.5 | $0.00000 | $0.00506 |
| Sonnet 5.5 | $0.00000 | $0.00253 |
| Haiku 4.5 | $0.00000 | $0.00127 |
Grade A, and why
domain-brainstorm 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Brainstorm
Kill criteria (read before running)
After ≥8 invocations, check the capability-brainstorm segment of core's proposal metrics report — run .hermit/bin/hermitd-run proposal metrics .hermit --source=capability-brainstorm (the project-resident bin/hermitd-run resolves core's plugin root, which a path relative to this plugin can't reach), or read the capability-brainstorm row of the table /hermitd:hermit-evolution prints. If triage-survival < 25% or PROP-acceptance < 30%, treat it as a class-level signal that brainstorm output is noisy and raise it with the operator — the segment is shared with core's capability-brainstorm and the other domain brainstorm skills, so it cannot by itself say which skill to cut.
Gate 0 — Gather inputs
Read these in parallel — all are cheap working-tree reads. Do not run the test suite or install tools.
Git activity
git log --oneline -50
git log --format= --name-only -50 | sort | uniq -c | sort -rn | head -20
Note the 5 most-churned files and any subsystem clusters.
Manifest drift
ls for package.json, Cargo.toml, pyproject.toml, go.mod. For each found, check its lockfile (package-lock.json/yarn.lock/pnpm-lock.yaml, Cargo.lock, poetry.lock, go.sum) exists alongside it. Flag any mismatch.
README coverage
Read README.md and a one-level ls of the repo root. Note features or modules claimed in the README with no corresponding directory or file visible.
Gate 1 — Generate ideas (max 2)
Think across all three inputs. For each candidate, both constraints must pass before including it:
- Concrete friction — state the operator pain in one sentence. What breaks, slows, or misleads today without this fix? If no specific pain, discard.
- ≥2 named grounding items: cite at least two by name (e.g.
git:cli/index.js,file:package-lock.json missing,readme:§Feature X). These support the friction; friction is the bar.
Map each passing idea to the closest dev prefix: [missing-tests], [tech-debt], [dependency], [tooling], or [architecture].
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 · 103 lines · 0 tokens per session scan A d0152b7b6592
domain-brainstorm is a skill published in the GitHub repository gtapps/hermitd (79 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,265 tokens. 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-02.
Other skills, from other repositories
apex-review
Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.
spine-review
API and backend code review — REST conventions, auth, validation, error handling, pagination, rate limiting, test coverage. Use when asked to "review this API", "code review", "review backend", or "pre-launch backend check".
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
superreview
Review a change set or explicit project scope for intent, correctness, safety, reuse, and maintainability; independently validate findings and produce one report without applying fixes.
init
Opt-in onboarding for the mARC agent team. Scaffolds a per-repo team binding so the team graduates from ephemeral session-memory to persistent, versioned config — without ever writing a file silently. Discovers the repo's org/repo/ project at runtime via gh, prefills {{ agentsdir }}/team.toml, and (optionally) a lean…