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/osiris-devworks/smart-citizen/begin_workgit clone --depth 1 https://github.com/Osiris-DevWorks/smart-citizenWhat 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.00038 | $0.01609 |
| Opus 5 | $0.00019 | $0.00805 |
| Sonnet 5 | $0.00008 | $0.00322 |
| Haiku 4.5 | $0.00004 | $0.00161 |
Grade A, and why
begin_work 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/begin_work
Bootstrap a work session for a GitHub issue. Resolves which release/X.Y.Z integration branch holds the work — reusing an existing unmerged branch when one fits, otherwise opening a new one by following the /start_release procedure — then creates a feature branch off it for the issue. After setup, drives the work in chunks with checkpoints between each stage so the user stays in the loop.
Work through every step in order. After each step, stop at the CHECKPOINT and wait for the user before proceeding.
Arguments
$ARGUMENTS — two whitespace-separated tokens, both required:
- issue — a GitHub issue URL (
https://github.com/Osiris-DevWorks/smart-citizen/issues/NN) or short form (#NN). The repo is implicit (Osiris-DevWorks/smart-citizen). - target release — either an explicit semver
X.Y.Z(e.g.1.4.3) or a bump type (major/minor/patch).
If either argument is missing or malformed, abort with: "/begin_work requires: <issue-url-or-#NN> <X.Y.Z | major | minor | patch>"
1. Parse and validate arguments
- Extract the issue number from URL or
#NNshorthand. - Validate the target release:
- Matches
^\d+\.\d+\.\d+$→ treat as explicit version. - Is
major/minor/patch→ compute the explicit version from currentVERSION.TXT(same math as/start_release). - Otherwise abort.
- Matches
2. Fetch and summarize the issue
gh issue view <NN> --json number,title,body,labels,state,url
- If
stateisclosed, warn the user. - Present a short summary: number, title, state, labels, and a one-paragraph summary of the body (keep it tight — the full body is in conversation context).
CHECKPOINT — confirm the issue summary captures the work, or correct it. Wait for the user.
3. Resolve the target release branch
Target is release/X.Y.Z (the version from step 1). Check the world in this order:
- Already merged to main:
git branch -r --merged origin/main | grep -F "origin/release/X.Y.Z". If matched, abort — "release/X.Y.Z is already merged to main; pick a higher target." - Exists locally:
git rev-parse --verify release/X.Y.Z. If yes,git checkout release/X.Y.Z. ConfirmVERSION.TXTon it equalsX.Y.Z. - Exists on origin only:
git ls-remote --heads origin release/X.Y.Z. If matched,git fetch origin release/X.Y.Z:release/X.Y.Z, then check out. ConfirmVERSION.TXT. - Does not exist anywhere: open it by following the procedure in
.claude/commands/start_release.md. Use the bump type the user passed; if they passed an explicit version, derive the bump type by diffing currentVERSION.TXT(onmain) againstX.Y.Z. The derived bump must be a single step (next patch, next minor, or next major). If the requested version skips ahead (e.g. current1.4.2→ requested1.6.0), abort and ask the user to clarify intent.
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 · 108 lines · 38 tokens per session scan A 72aee8ba9716
begin_work is a command published in the GitHub repository Osiris-DevWorks/smart-citizen (99 stars, last pushed 3d ago), licensed Apache-2.0. It adds 38 tokens to every session and 1,609 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-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.