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/higoralves/orc/scaffoldgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/commands/higoralves/orc/scaffold)<a href="https://agentmods.dev/commands/higoralves/orc/scaffold"><img src="https://agentmods.dev/badge/commands/higoralves/orc/scaffold.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.00040 | $0.00696 |
| Opus 5 | $0.00020 | $0.00348 |
| Sonnet 5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:scaffold
Stand up a new package/service shell with the structure that future-you will not regret. Strictly the skeleton — no business logic, no fake examples.
Arguments
<name>— package or service name (kebab-case).--type—lib(default),service,app,cli. Affects the initial directory layout.
Workflow
Phase 1 — Confirm intent
Print the Gate headline (**⛔ Gate — scaffold shape**, per orc:callouts), then AskUserQuestion:
- Where does this live? (project root /
packages/<name>//services/<name>//apps/<name>/) - Language? (TypeScript / Go / Rust / Python)
- License? (MIT / Apache-2.0 / inherit from repo)
Phase 2 — Initialize
Create the directory. Run the appropriate init for the language (npm init -y, go mod init, cargo init, python -m venv + pyproject.toml).
Phase 3 — Author README
Invoke orc:readme-writing. The skill writes a README with the standard sections (What / Why / Install / Usage / Test / License). Adjust to type-specific bits (services include "Run", apps include "Dev server").
Phase 4 — Author docs
Invoke orc:documentation-writing. Set up the Diátaxis structure under docs/:
docs/tutorial/— getting-started flowsdocs/how-to/— task recipesdocs/reference/— API/CLI/config referencedocs/explanation/— concepts, architecture
Create a stub docs/README.md linking the four quadrants.
Phase 5 — First failing test
Invoke orc:tdd. Write the simplest possible failing test for the package/service entry point. Run the suite — it must fail meaningfully.
Phase 6 — First commit
Invoke orc:git-commit. Conventional Commits format. Title: chore(scaffold): initialize <name> package or similar. Body lists what was scaffolded.
Output
- New directory with proper layout for the chosen type
README.md,docs/Diátaxis quadrants, license file- One failing test, one commit
- Echo the path to the new package, then close with the handoff:
> **➡️ Next**
>
> Run `/orc:start` to begin real work in `<path>`.
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 · 77 lines · 40 tokens per session scan A ae9eac3c32b5
scaffold is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 696 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
uninstall
Remove flow-next files from project.
refine-title
深度分析 Issue 或 PR 内容，并将其标题重构为 Conventional Commits 格式.