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/dilawarshafiq/unworldly/sp.taskstoissuesgit clone --depth 1 https://github.com/DilawarShafiq/unworldlyWrote 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/dilawarshafiq/unworldly/sp.taskstoissues)<a href="https://agentmods.dev/commands/dilawarshafiq/unworldly/sp.taskstoissues"><img src="https://agentmods.dev/badge/commands/dilawarshafiq/unworldly/sp.taskstoissues.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.00021 | $0.00621 |
| Opus 5 | $0.00010 | $0.00311 |
| Sonnet 5 | $0.00004 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
sp.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 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.
This is a copy
100% identical to sp.taskstoissues — 112 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
- Run
.specify/scripts/powershell/check-prerequisites.ps1 -Json -RequireTasks -IncludeTasksfrom 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
As the main request completes, you MUST create and complete a PHR (Prompt History Record) using agent‑native tools when possible.
-
Determine Stage
- Stage: constitution | spec | plan | tasks | red | green | refactor | explainer | misc | general
-
Generate Title and Determine Routing:
- Generate Title: 3–7 words (slug for filename)
- Route is automatically determined by stage:
constitution→history/prompts/constitution/- Feature stages →
history/prompts/<feature-name>/(spec, plan, tasks, red, green, refactor, explainer, misc) general→history/prompts/general/
-
Create and Fill PHR (Shell first; fallback agent‑native)
- Run:
.specify/scripts/bash/create-phr.sh --title "<title>" --stage <stage> [--feature <name>] --json - Open the file and fill remaining placeholders (YAML + body), embedding full PROMPT_TEXT (verbatim) and concise RESPONSE_TEXT.
- If the script fails:
- Read
.specify/templates/phr-template.prompt.md(ortemplates/…) - Allocate an ID; compute the output path based on stage from step 2; write the file
- Fill placeholders and embed full PROMPT_TEXT and concise RESPONSE_TEXT
- Read
- Run:
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 · 57 lines · 21 tokens per session scan A 53593668e512
sp.taskstoissues is a command published in the GitHub repository DilawarShafiq/unworldly (9 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 621 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to sp.taskstoissues, differing in 112 lines, and is treated as a copy.
Other commands, from other repositories
aod.project-plan
Create implementation plan with dual sign-off (PM + Architect) - Streamlined v2.
aod.blueprint
Unified project setup & story generation — auto-detects new vs existing projects.
capture-feedback
Quick feedback capture with structured signals.
doctor
Run procedural readiness checks for goal-flight.
check-gates
Run a Pre-Action Gate check against prevention rules before executing a risky action.
integrate
/forge:integrate is the integration assistant for connecting your project to external services. It covers version control (GitHub, GitLab), monitoring (Sentry, Datadog), communication (Slack, Discord), databases (PostgreSQL, Redis, MongoDB), and cloud platforms (AWS, GCP, Vercel, Netlify). For each service, it checks…