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 toBzh30/Claude-Project-Bootstrap --skill grill-with-docsgit clone --depth 1 https://github.com/toBzh30/Claude-Project-BootstrapWrote 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/tobzh30/claude-project-bootstrap/grill-with-docs)<a href="https://agentmods.dev/skills/tobzh30/claude-project-bootstrap/grill-with-docs"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/grill-with-docs/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/tobzh30/claude-project-bootstrap/grill-with-docs"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/grill-with-docs.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.00073 | $0.00828 |
| Opus 5 | $0.00036 | $0.00414 |
| Sonnet 5 | $0.00015 | $0.00166 |
| Haiku 4.5 | $0.00007 | $0.00083 |
Grade A, and why
grill-with-docs 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask the questions one at a time, waiting for feedback on each question before continuing.
If a question can be answered by exploring the codebase, explore the codebase instead.
Domain awareness
During codebase exploration, also look for existing documentation:
File structure
This marketplace's convention is a CLAUDE.md hub that links spoke docs under .claude/rules/:
/
├── CLAUDE.md ← hub; links the spokes below
├── .claude/
│ └── rules/
│ ├── glossary.md ← domain glossary (this skill maintains it)
│ └── decisions.md ← decision log (append-only, dated entries)
└── src/
For a large or multi-area codebase, the CLAUDE.md hub links multiple spoke docs (that hub is the map); a big domain may split its glossary into several spokes (e.g. .claude/rules/glossary-ordering.md) all linked from the hub. Infer which spoke the current topic relates to; if unclear, ask.
Create files lazily — only when you have something to write. If no .claude/rules/glossary.md exists, create it when the first term is resolved. Append to .claude/rules/decisions.md (creating it if absent) when the first decision is worth logging.
During the session
Challenge against the glossary
When the user uses a term that conflicts with the existing language in .claude/rules/glossary.md, call it out immediately. "Your glossary defines 'cancellation' as X, but you seem to mean Y — which is it?"
Sharpen fuzzy language
When the user uses vague or overloaded terms, propose a precise canonical term. "You're saying 'account' — do you mean the Customer or the User? Those are different things."
Discuss concrete scenarios
When domain relationships are being discussed, stress-test them with specific scenarios. Invent scenarios that probe edge cases and force the user to be precise about the boundaries between concepts.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 75 lines · 73 tokens per session scan A 401434a3c0e9
grill-with-docs is a skill published in the GitHub repository toBzh30/Claude-Project-Bootstrap (3 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 828 once invoked, about $0.0004 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
project-standard-spec
Spec maintainer for Big Emotion Project Standard. Reads Confluence (Requirements / Decisions / Architecture) as the source of truth, helps you investigate a problem, structures the reflection, and produces drafts — Pending REQ/DEC/ARCH sections on Confluence + matching Jira tickets in the Jira project configured in…
fix-ci-train
Batch-fix the CI on every open pull request whose required checks are red — CI only, no review, no merge. From a GitHub PRs URL (or the current repo), enumerate every open PR with failing required checks, fetch each PR's failing-check logs, consolidate a per-PR CI-fix checklist, dispatch a team of parallel fixer…
issue-train
Batch-process every open GitHub issue in a list — triage, detect existing PR linkage, detect silent fixes in already-merged PRs, close issues that are no longer pertinent, then plan + build + open one PR per remaining actionable issue with Closes.
blueprint
Extract a complete specs/ directory from any frontend codebase. Covers all 12 axes needed to rebuild or migrate a frontend app. Produces 80% quality on first pass, refined to 95% through guided iteration.
fix-train
Batch-apply the requested changes on every open pull request in a GitHub list — fix only, no merge. From a GitHub PRs URL (or the current repo), enumerate every open PR, collect each PR's requested changes (formal CHANGESREQUESTED reviews, inline review comments, and "Issues requiring changes" comments /…
project-standard-audit
Production-readiness audit for Big Emotion Project Standard (this repo). Read-only multi-domain scored assessment that answers four questions — is the plugin ready to install on real repos, is the template surface healthy, what is the security posture, and is the score close to 8–9/10. Use when the user asks "is it…