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/thettwe/nyann/bootstrap-projectnpx skills add thettwe/nyann --skill bootstrap-projectgit clone --depth 1 https://github.com/thettwe/nyannWrote 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/thettwe/nyann/bootstrap-project)<a href="https://agentmods.dev/skills/thettwe/nyann/bootstrap-project"><img src="https://agentmods.dev/badge/skills/thettwe/nyann/bootstrap-project.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.00252 | $0.04276 |
| Opus 5 | $0.00126 | $0.02138 |
| Sonnet 5 | $0.00050 | $0.00855 |
| Haiku 4.5 | $0.00025 | $0.00428 |
Grade A, and why
bootstrap-project 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bootstrap-project
You are executing nyann's main bootstrap flow. The goal is to take an empty directory, a fresh repo, or an existing messy repo and bring it up to the conventions in a nyann profile — without silently mutating anything.
Work in phases. Each phase is one or more bash scripts in bin/. Never run a destructive
action outside a preview-confirmed plan. If a phase emits a structured skip record
({"skipped": "...", "reason": "..."}), log it in your final summary and continue with the
remaining phases.
0. Team profile freshness check (quick, non-blocking)
Run bin/check-team-staleness.sh before starting. If it produces
output, show the notification to the user (e.g. "Your team profiles
have upstream changes. Run /nyann:sync-team-profiles to update
before bootstrapping, or continue with the current versions.").
Do not block — let the user decide whether to sync first.
1. Detect
- Run
bin/detect-stack.sh --path <target>and capture the JSON to a temp file (e.g.bin/detect-stack.sh --path <target> > "${TMPDIR:-/tmp}/nyann-stack.json") so step 2 can pass it via--stack. Never proceed without it. - If
confidence < 0.6, tell the user what you found and ask them to confirm the stack before continuing. Show the top two or three reasoning entries so they can see why you chose what you chose. - If
is_monorepois true, note it — bootstrap will auto-resolve per-workspace configs (hooks, lint-staged entries, commit scopes) usingbin/resolve-workspace-configs.sh.
See references/python.md and references/javascript.md for stack-specific notes Claude should
fold into its follow-ups. Only load them when the detected stack matches.
2. Pick a profile
Three branches:
- User named a profile. Load it with
bin/load-profile.sh <name>. If the loader exits 2 (profile not found), list the available profiles it reported and ask the user to pick one. - No profile named. Run
bin/suggest-profile.sh --target <repo> --stack <stack-json-file>to get a ranked list of matching profiles with confidence scores. Pass the StackDescriptor JSON captured in step 1 via--stackso the script reuses it instead of re-running detect-stack.sh (which would duplicate the directory walk).
What ships with it
4 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.
- 4d ago First seen · 360 lines · 252 tokens per session scan A 385efad37cae
bootstrap-project is a skill published in the GitHub repository thettwe/nyann (6 stars, last pushed 5d ago), licensed MIT. It adds 252 tokens to every session and 4,276 once invoked, about $0.0013 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
frontend-design
Use when building UI components, making design decisions for frontend work, reviewing UI implementation quality, or planning interaction patterns.
design-system-quality
Use when reviewing UI/frontend code, conducting PR reviews for components, checking design system compliance, or after any UI component work.
brand-guidelines
Use when user mentions "brand", "Open Session colors", "Aperol", "Charcoal", "Vanilla", "brand guidelines", or works on UI following Open Session standards.
design-system
Generate a context-aware, production-grade design system from the SDL blueprint. Produces design tokens, typography, palette, motion language, and component inventory — grounded in the product domain, audience, and architecture. Use this skill when generating or refining the SDL design section, scaffolding frontend…
wireframe-patterns
JSON wireframe spec patterns — SDL-to-screen mapping and section examples for each screen type.
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…