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 skills add fabio-barboza/development-orchestrator --skill do-statusgit clone --depth 1 https://github.com/fabio-barboza/development-orchestratorWrote 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/skills/fabio-barboza/development-orchestrator/do-status)<a href="https://agentmods.dev/skills/fabio-barboza/development-orchestrator/do-status"><img src="https://agentmods.dev/badge/skills/fabio-barboza/development-orchestrator/do-status.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.00793 |
| Opus 5 | $0.00034 | $0.00396 |
| Sonnet 5 | $0.00014 | $0.00159 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
do-status 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 8d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Status Report
Directory Convention
MANDATORY: PRD directories ALWAYS follow the pattern ./prds/prd-[feature-slug]/ where prd- is a required prefix. Example: feature user-auth → directory ./prds/prd-user-auth/. When scanning ./prds/, only consider folders matching the prd-* pattern.
Procedures
Step 1: Identify Target PRD
- If the user did not provide
[feature-slug], scan./prds/for folders matchingprd-*. - If only one
prd-*folder exists, use it automatically. If multiple exist, select the most recently modified. - If
./prds/does not exist or contains noprd-*folders, halt: "No PRDs found — rundo-create-prdfirst."
Step 2: Read Tasks
- Read
./prds/prd-[feature-slug]/tasks/tasks.md. If it does not exist, halt: "tasks.md not found — rundo-create-tasksfirst." - Parse all tasks:
[x]= completed,[ ]= pending. - Identify the next pending task (first
[ ]in order). - Check if the next pending task has unmet dependencies (any prior task still
[ ]).
Step 3: Check Artifact Integrity (Optional)
- For each task marked
[x], verify its review file exists at./prds/prd-[feature-slug]/tasks/[num]_task_review.md. - Flag any
[x]task missing its review file as incomplete. - If the next pending task is currently in progress, read
./prds/prd-[feature-slug]/tasks/[num]_task.mdto show subtask-level progress.
Step 4: Output Status Report
Produce a concise report in this format:
📦 [Feature Name] (prd-[slug])
Progresso: X/Y tasks concluídas (Z%)
✅ Concluídas: 1, 2, 3
⏳ Próxima: 4 — [título da task]
⏸️ Pendentes: 5, 6, 7 ... Y
⚠️ Artefatos ausentes: [lista de tasks [x] sem review file, se houver]
🚫 Bloqueios: [tasks com dependências não atendidas, se houver]
Output Language
Report in Brazilian Portuguese (PT-BR).
Error Handling
- If
./prds/does not exist or contains noprd-*folder, halt with: "No PRDs found — rundo-create-prdfirst." - If
tasks.mddoes not exist for the selected PRD, halt with: "tasks.md not found — rundo-create-tasksfirst." - If multiple
prd-*folders exist and none was specified, select the most recently modified — never block on user input. - If a task is marked
[x]but its review file is missing, list the inconsistency under "Artefatos ausentes" — do not modify any file.
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.
- 8d ago First seen · 58 lines · 69 tokens per session scan A e65471801e2c
do-status is a skill published in the GitHub repository fabio-barboza/development-orchestrator (28 stars, last pushed 9d ago), licensed MIT. It adds 69 tokens to every session and 793 once invoked, about $0.0003 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.