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/longranger2/project-doc-bootstrap/project-doc-bootstrapnpx skills add longranger2/project-doc-bootstrap --skill project-doc-bootstrapgit clone --depth 1 https://github.com/longranger2/project-doc-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/longranger2/project-doc-bootstrap/project-doc-bootstrap)<a href="https://agentmods.dev/skills/longranger2/project-doc-bootstrap/project-doc-bootstrap"><img src="https://agentmods.dev/badge/skills/longranger2/project-doc-bootstrap/project-doc-bootstrap.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.00073 | $0.01075 |
| Opus 5 | $0.00036 | $0.00537 |
| Sonnet 5 | $0.00015 | $0.00215 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
project-doc-bootstrap 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Doc Bootstrap
Use this skill to set up a repository so future AI sessions can reach useful context in a few reads instead of re-deriving structure from source every time.
Default convention:
CLAUDE.mdis the source of truth.AGENTS.mdis a sibling symlink toCLAUDE.md.- Every directory that has a
CLAUDE.mdmust also have anAGENTS.mdsymlink as a sibling. This is a hard invariant — never create one without the other. - Docs follow a fractal hierarchy: L1 root guide, L2 directory guides, L3 file-header notes only where needed.
If the user explicitly wants different filenames or a different source-of-truth file, adapt the convention. Otherwise default to CLAUDE.md + AGENTS.md.
When to Use
Use this skill when the user wants to:
- initialize a new project's AI-facing docs
- set up
CLAUDE.md/AGENTS.md - design a directory-level documentation hierarchy
- make a repo easier for AI to understand and maintain
- standardize how docs are updated when files move or modules grow
- install a pre-commit hook that enforces doc-sync at commit time
Quick Start Workflow
- Read
references/blueprint.mdto choose the documentation model. - Read
references/workflow.mdto bootstrap the repo in the right order. - Read
references/templates.mdfor ready-to-copy templates: CLAUDE.md skeletons, symlink commands, and pre-commit hook scripts.
Core Outcomes
By the end of the task, the repo should have:
- one root
CLAUDE.mdthat explains architecture, rules, and the doc system - one root
AGENTS.md -> CLAUDE.mdsymlink - L2 docs for top-level and core module directories
- L2 docs for subdirectories that cross the documentation threshold
- explicit rules for when new L2 docs should be created later
- a pre-commit hook (
.git/hooks/pre-commit) that warns when staged source files are in a documented directory whoseCLAUDE.mdwas not also staged (hook is local-only, not committed) - a verification pass confirming symlink integrity, hook installation, and obvious gaps
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.
- 3d ago First seen · 93 lines · 73 tokens per session scan A 862c7d0ffa9b
project-doc-bootstrap is a skill published in the GitHub repository longranger2/project-doc-bootstrap (2 stars, last pushed 4mo ago), licensed MIT. It adds 73 tokens to every session and 1,075 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
acontext-installer
Install Acontext, Login & Init Acontext Project, Add Skill Memory to Agent.
init
把这个 agent 项目模板初始化成一个真实项目——通过分阶段访谈问清项目定位、技术栈、领域概念、红线和范围，然后填充 AGENTS.md 与 docs/ 里的所有 TODO(init) 占位。当用户说"初始化项目"、"应用这个模板"、"帮我把项目建起来"、"续问 init"、"接着上次的问题继续"，或者 AGENTS.md 顶部还有「这个仓库还没初始化」引用块时使用。.
codex-fable5
Apply a Claude Fable 5 inspired operating style inside Codex. Use when the user asks to make Codex act like Fable, Fable5, fablize, or Value-for-Fable/VFF; convert Anthropic or Claude system-prompt/tool instructions to Codex; set up a Fable-style tool-first workflow with goal gates, investigation, verification…
maintain-context
当 scripts/audit-context.mjs 报 error/warning、学习收件箱有积压待合并，或用户说"文档该更新了"、"上下文体检"、"agent 好像不懂这个项目了"、要整理规则、一个里程碑结束需要收尾时使用：体检并更新本仓库的 agent 上下文文件（AGENTS.md、.agents/skills、docs/）。.
ship-change
完整交付一个功能或一次改动的标准流程，从确认范围、实现、自测到收尾同步文档。当用户说"做一下 X 功能"、"实现"、"加个"、"改一下"这类需要动代码的任务时使用，尤其是改动会跨多个文件的时候。.
record-decision
把一个有取舍的技术决策写成 ADR 存进 docs/decisions/。当用户说"记一下这个决定"、"写个 ADR"、"为什么选了 X"、"这个方案定下来了"，或刚刚在两个方案之间做出选择时使用。.