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 commands/danielbodnar/skills/scaffoldgit clone --depth 1 https://github.com/danielbodnar/skillsWhat 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.00020 | $0.00527 |
| Opus 5 | $0.00010 | $0.00264 |
| Sonnet 5 | $0.00004 | $0.00105 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
scaffold 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 2d 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.
What it actually says
Scaffold a new project in the current directory with standard configuration files.
Steps
Detect the project type from context clues (existing files, user input, directory name). If ambiguous, ask the user which type: bun, cloudflare-workers, rust, or rust-bun.
Create .mise.toml
Generate a .mise.toml file appropriate for the detected project type. Use the templates from the mise-config skill. Always include just = "latest".
Create justfile
Generate a justfile with recipes appropriate for the project type. Use the templates from the justfile-patterns skill. Always set shell := ["nu", "-c"] and include a default recipe that runs just --list.
Create .editorconfig
Generate a standard .editorconfig:
root = true
[*]
end_of_line = lf
charset = utf-8
indent_style = space
indent_size = 2
insert_final_newline = true
trim_trailing_whitespace = true
[*.md]
trim_trailing_whitespace = false
[Makefile]
indent_style = tab
[justfile]
indent_style = space
indent_size = 4
Create .gitignore
Generate a .gitignore appropriate for the project type. Always include:
# Dependencies
node_modules/
# Build output
dist/
# Cache and scratch
.cache/
.scratch/
.agents/
# Environment
.env
.env.*
!.env.example
.dev.vars
# OS
.DS_Store
Thumbs.db
# IDE
.idea/
*.swp
*.swo
*~
# Bun
bun.lockb
# Test coverage
coverage/
For Rust projects, also add:
# Rust
target/
Cargo.lock
For Cloudflare Workers, also add:
# Wrangler
.wrangler/
Initialize git (if not already a repo)
If the current directory is not already a git repository, initialize one with git init.
Summary
After creating all files, list what was generated and suggest next steps:
mise trustto activate tool versionsmise installto install the toolsjustto see available recipes- Create
package.json(for Bun projects) orCargo.toml(for Rust projects) if not present
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.
- 2d ago First seen · 112 lines · 20 tokens per session scan A f83bad8c0978
scaffold is a command published in the GitHub repository danielbodnar/skills (2 stars, last pushed 24d ago), licensed MIT. It adds 20 tokens to every session and 527 once invoked, about $0.0001 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.