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/third-order-labs/longform-plugin/project-scaffoldingnpx skills add third-order-labs/longform-plugin --skill project-scaffoldinggit clone --depth 1 https://github.com/third-order-labs/longform-pluginWrote 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/third-order-labs/longform-plugin/project-scaffolding)<a href="https://agentmods.dev/skills/third-order-labs/longform-plugin/project-scaffolding"><img src="https://agentmods.dev/badge/skills/third-order-labs/longform-plugin/project-scaffolding.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.00039 | $0.03519 |
| Opus 5 | $0.00019 | $0.01759 |
| Sonnet 5 | $0.00008 | $0.00704 |
| Haiku 4.5 | $0.00004 | $0.00352 |
Grade A, and why
project-scaffolding 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 5d 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 — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Scaffolding
This skill provides the complete template library and directory conventions for long-form fiction projects. It defines the standard project structure, file naming rules, and templates for every document type the project might eventually need.
Important: These templates are a library, not a checklist. /start-project creates only the core documents the project needs immediately (pitch, characters, continuity — and conditionally world, outline, or north-star). Other documents are created later, when the project's complexity warrants them. The commands /write-chapter and /wrap contain the logic for when to propose each document. This skill provides the template to use when that moment arrives.
Directory Conventions
The full project structure when all documents have been created. A new project starts with only a few docs and grows into this over time:
project-root/
├── AGENTS.md # Agent workflow rules and defaults
├── docs/ # All planning and tracking documents
│ ├── 00-pitch.md # Always created at start
│ ├── 01-north-star.md # Created at start if user has clarity
│ ├── 02-world.md # Created at start if world needs definition
│ ├── 03-characters.md # Always created at start
│ ├── 04-outline.md # Created at start if user has structural vision
│ ├── 05-glossary.md # Proposed when 10+ invented terms accumulate
│ ├── 06-scene-log.md # Proposed after first chapter is drafted
│ ├── 07-continuity.md # Always created at start
│ ├── 08-voice.md # Proposed after 3-5 chapters or via /voice-session
│ ├── 09-chapter-outline-template.md # Emerges from first few outlines
│ ├── 13-threads.md # Proposed when 3+ subplots are running
│ ├── 19-foreshadowing-checklist.md # Proposed when deliberate seeds are planted
│ └── 25-style-guide.md # Proposed after 3-5 chapters when patterns stabilize
├── outlines/ # Chapter outlines by volume
│ ├── book-one/
│ ├── book-two/
│ └── book-three/
├── draft/ # Draft chapters by volume
│ ├── book-one/
│ ├── book-two/
│ └── book-three/
└── manuscript/ # Final assembled manuscript
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.
- 5d ago First seen · 487 lines · 39 tokens per session scan A 5260d133e7fc
project-scaffolding is a skill published in the GitHub repository third-order-labs/longform-plugin (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 3,519 once invoked, about $0.0002 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
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…
miniapp-dev
Develops, maintains, and generates BitFun MiniApps (Zero-Dialect Runtime). Use when (1) working on miniapp framework code under src/crates/assembly/core/src/miniapp/ or src/web-ui/src/app/scenes/miniapps/; or (2) generating / creating / designing a NEW MiniApp for the user — including any request like "做一个小应用 / 生成…
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
investigate
Systematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug…