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.
git clone --depth 1 https://github.com/Chappygo-OS/Atomic-SpecWrote 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/chappygo-os/atomic-spec/taskstoissues)<a href="https://agentmods.dev/commands/chappygo-os/atomic-spec/taskstoissues"><img src="https://agentmods.dev/badge/commands/chappygo-os/atomic-spec/taskstoissues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/chappygo-os/atomic-spec/taskstoissues"><img src="https://agentmods.dev/badge/commands/chappygo-os/atomic-spec/taskstoissues.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00481 |
| Opus 5.5 | $0.00008 | $0.00192 |
| Sonnet 5.5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
taskstoissues 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 1mo 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
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Registry Protocol (Constitution Directive 7)
Follow _registry-protocol.md:
- On entry: Read
specs/_defaults/registry.yaml. Focus onintegrations.issue_tracker(labels, project/board mapping, assignee conventions) andconventions.labelsso created issues inherit project-wide taxonomy. - During: When you are about to create an issue with a new label, project, or milestone that isn't in the registry, apply Scenario A/B/C from the protocol (re-use, add-to-registry via HITL, or deviate with documentation).
- On exit: If the issue-creation pass introduced new label schemes or tracker conventions, HITL-prompt the user to persist them in
integrations.issue_tracker/conventions.labels.
If the registry file is absent, warn and proceed without defaults (graceful degradation).
Outline
- Run
{SCRIPT}from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). - From the executed script, extract the path to tasks.
- Get the Git remote by running:
git config --get remote.origin.url
[!CAUTION] ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS A GITHUB URL
- For each task in the list, use the GitHub MCP server to create a new issue in the repository that is representative of the Git remote.
[!CAUTION] UNDER NO CIRCUMSTANCES EVER CREATE ISSUES IN REPOSITORIES THAT DO NOT MATCH THE REMOTE URL
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.
- 1mo ago First seen · 44 lines · 21 tokens per session scan A 7b483ff5a74f
taskstoissues is a command published in the GitHub repository Chappygo-OS/Atomic-Spec (10 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 481 once invoked, about $0.0001 per session on Opus 5.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
taskstoissues
A command that turns structured tasks from project design documents into ordered GitHub Issues, written in simplified Chinese.
ops-standup
Morning briefing: commits, PRs, CI, blockers and priorities of the day.
bulk-import-issues
Bulk import GitHub issues to Linear.
ijfw-status
Show IJFW state -- mode, routing, memory, recent activity, codebase index, settings. Use when you want the at-a-glance banner you'd otherwise get at session start.
resume-project
Run resume-project now — Now / Blocked / Next. Not a cheat sheet.
task-close
Close a whole finished task: verify the spec done-conditions, set TASKSTATE.md to its final closed state, and move the folder from active/ to archive/. Use when all slices are closed, the work is merged or explicitly waived, and the task is ending. Do not use for one slice (use slice-closure), unfinished work…