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 skills/fabio-barboza/development-orchestrator/do-sharednpx skills add fabio-barboza/development-orchestrator --skill do-sharedgit 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-shared)<a href="https://agentmods.dev/skills/fabio-barboza/development-orchestrator/do-shared"><img src="https://agentmods.dev/badge/skills/fabio-barboza/development-orchestrator/do-shared.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.00058 | $0.00466 |
| Opus 5 | $0.00029 | $0.00233 |
| Sonnet 5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
do-shared 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.
What it actually says
Shared Resources
Purpose
Centralizes references consumed by multiple do-* execution skills. Avoids duplication of the MCP capability registry and the discovery procedure across skills.
Contents
references/do-mcp-capabilities.md: Registry mapping each configured MCP server to its capabilities, tool prefix, runtime requirements, and unavailability handling.references/do-mcp-discovery-instructions.md: Standard procedure for discovering MCP servers in the active AI tool's configuration file and applying the capability guard.references/do-service-readiness.md: Standard procedure for checking, reusing, and starting services (frontend dev server, backend API, broker, database) before invoking MCP tools or E2E tests. Enforces "check first, reuse if running, start only when needed, never kill running services".
Consumers
The following skills read these references at runtime:
do-execute-taskdo-execute-qado-execute-qa-bugfixdo-execute-review
Usage
This skill is not user-invocable. Other do-* skills cite the absolute path (e.g., do-shared/references/do-mcp-capabilities.md) when their procedure requires the registry or the discovery flow.
Error Handling
- If a consumer skill cannot locate
do-shared/references/do-mcp-capabilities.md, halt and report the missing dependency — do not fall back to hardcoded MCP assumptions. - If a new MCP is configured by the user but absent from the registry, add an entry to
do-shared/references/do-mcp-capabilities.mdfollowing the existing schema; no skill code needs to change.
References
- MCP Registry:
do-shared/references/do-mcp-capabilities.md - MCP Discovery:
do-shared/references/do-mcp-discovery-instructions.md - Service Readiness:
do-shared/references/do-service-readiness.md
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 34 lines · 58 tokens per session scan A 9718221eb32b
do-shared is a skill published in the GitHub repository fabio-barboza/development-orchestrator (28 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 466 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…