Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/skills/setup-bootstrap/SKILL.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/setup-bootstrap)<a href="https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/setup-bootstrap"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/setup-bootstrap/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/moberghr/mtk-agent-toolkit/setup-bootstrap"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/setup-bootstrap.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.00036 | $0.06779 |
| Opus 5.5 | $0.00014 | $0.02712 |
| Sonnet 5.5 | $0.00007 | $0.01356 |
| Haiku 4.5 | $0.00004 | $0.00678 |
Grade C, and why
setup-bootstrap scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Run `mkdir`, `rm -rf` and `echo >` as separate Bash calls: conservative permission modes reject a chain containing `rm -rf`, which aborts the whole chain. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Existing `.claude/settings.json`:** if it carries legacy `permissions.allowedTools`, first run `bash "${CLAUDE_PLUGIN_ROOT}/scripts/migrate-settings-permissions.sh" .claude/settings.json` (and on `.claude/settings.lo How it starts
The opening of the file, as written. The whole thing — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MTK Setup Bootstrap — Prepare Repository for AI-Assisted Development
MTK File Resolution
Resolve MTK skill/reference/script paths per .claude/references/mtk-file-resolution.md unless the router already stated MTK_ROOT=<path> this session; AGENTS.md, CLAUDE.md, .claude/tech-stack, .claude/rules/, tasks/, docs/, .mtk/ stay project-relative.
Companion files: several steps defer detail to .claude/references/*.md. If a companion cannot be resolved at read time, stop that step and report the missing path — do not reconstruct its content from memory.
You detect the tech stack, audit the codebase, and generate a tailored AGENTS.md — the canonical constitution every harness reads — plus the CLAUDE.md shim that imports it. The implementation and review agents use them as their source of truth.
Modes
--preview— run detection, scan and interview, then show the proposed AGENTS.md + shim + rules diff and confirm viaAskUserQuestionbefore writing anything.--non-interactive— skip the STEP 2.5 interview.--no-verify-commands— skip STEP 3.5a's command verification: nothing is executed, and the Tech Stack section gets no<!-- verified: ... -->stamp and no[UNVERIFIED]annotations. The STEP 5 report saysCommand verification: skipped via --no-verify-commands.
The flags combine.
Generation Constraints
Compliance with constitution rules degrades as the instruction count grows, and generated constitutions that list everything perform worst. So:
- Root AGENTS.md: target 60–80 lines, hard cap 120. Detail goes to
.claude/rules/or a hook. TheCLAUDE.mdshim is ~20 lines with no rule text. - Trigger-action rules with the reason attached (
When X, do Y — because Z). Write prohibitions only for constraints the codebase actually enforces (the counter-example gate in STEP 3 decides). NoIMPORTANT:/YOU MUSTmarkers: they cause over-triggering. - Mechanize what you can. A rule a hook or the
settings.jsondeny list enforces is not repeated in AGENTS.md. - No aspirational rules, no list-of-everything. Every rule comes from an observed pattern or failure in this codebase; omit what the model can read from the code.
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 Changed 62156517bcf5
- 13d ago Changed · +4 lines c85bc386da0b
- 16d ago Changed · -235 lines e7d65f4429f5
- 1mo ago Changed · +13 lines · +6 tokens per session 623b14ed47cd
- 1mo ago Changed · -7 lines scan D → C 4bce6e30b3e5
- 1mo ago Changed f34424408b5f
- 2mo ago First seen · 535 lines · 30 tokens per session scan D 9a512fc82cb6
setup-bootstrap is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (9 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 6,779 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…