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/doctly/switchboard/releasegit clone --depth 1 https://github.com/doctly/switchboardWhat 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.00000 | $0.00482 |
| Opus 5 | $0.00000 | $0.00241 |
| Sonnet 5 | $0.00000 | $0.00096 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
release 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
Perform a release for this project. Steps:
- Find the most recent version tag with
git describe --tags --abbrev=0and collect all commits between it and HEAD usinggit log {prev_tag}..HEAD --format="%B---" - Bump the version with
npm version patch --no-git-tag-version - Commit the version bump with message:
v{version}: {short summary of changes} - Create a git tag
v{version} - Push commits and tag:
git push && git push --tags - Wait for the GitHub Actions build to complete using
gh run watchon the latest run - Once the build finishes and creates a draft release, publish it with release notes using
gh release edit v{version} --draft=false --notes "..." - Release notes format:
Group changes by category (e.g. "Features", "Bug Fixes", "Performance Improvements", etc.).## What's Changed ### {Category} - {change description} ### {Category} - {change description}
Writing the release notes
Write them for the person using the app, not for someone reading the git log. Read every commit between the tags so nothing user-facing gets missed — but the notes describe what changed for the user, they are not a summary of each commit.
Each entry says what the user will notice: what the app did before, what it does now. Don't name internal symbols, columns, migrations, or files.
Leave out:
- Fixes for bugs introduced after the previous tag. The user never ran that code, so there's nothing to announce. Describe only the net change since the last release.
- Refactors, schema migrations, test-only changes, and dev tooling with no visible effect.
- Cosmetic tweaks too small to notice — padding, font sizes, color nudges.
- Anything not confirmed to actually work. If a change is unverified or known broken, raise it before publishing instead of listing it.
Collapse a feature and its follow-up fixes into a single entry describing where things landed. Several commits often add up to one user-facing change; one commit sometimes makes several.
A short release with three real entries beats a padded one with twelve. If nothing user-facing changed, say so plainly.
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 · 38 lines · 0 tokens per session scan A fc8c738d134a
release is a command published in the GitHub repository doctly/switchboard (329 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 482 tokens. 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-30.
Other commands, from other repositories
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.