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 tdwhere123/do-it --skill do-it-architecturegit clone --depth 1 https://github.com/tdwhere123/do-itWrote 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/tdwhere123/do-it/do-it-architecture)<a href="https://agentmods.dev/skills/tdwhere123/do-it/do-it-architecture"><img src="https://agentmods.dev/badge/skills/tdwhere123/do-it/do-it-architecture/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/skills/tdwhere123/do-it/do-it-architecture"><img src="https://agentmods.dev/badge/skills/tdwhere123/do-it/do-it-architecture.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00300 |
| Opus 5.5 | $0.00011 | $0.00120 |
| Sonnet 5.5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
do-it-architecture 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
Architecture
Locate the load-bearing path from entry through mutation and accepted state to visible effect and recovery. Distinguish public, persisted, cross-boundary, and private surfaces; the narrowest actual compatibility promise matters.
Separate semantic authority (meaning and legal states), admission (permitted input or mutation), projection (derived views), and recovery (committed, retry, repair, or reconcile). One semantic authority does not require one physical writer. Place policy with the owner of end-to-end intent.
Ask whether a valid path bypasses a proposed guard and whether the rule would remain if its current layer were replaced. Derived caches and copies should not silently become competing authorities.
Explore applicable denial, duplication, races, replay, cancellation, timeout, and partial or uncertain commit. Identify the recovery owner and the invariant that survives failure. For a boundary change, account for consumers, compatibility, migration, rollback, and eventual retirement.
Challenge necessity before adding an abstraction, service, or governance layer. An independent strategist can test premises without inheriting the author's conclusion. Use architecture rationale or the stateful scan where their detail helps; a private reversible choice does not need a dossier.
What ships with it
1 file 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.
- 1mo ago Changed · -55 lines · -9 tokens per session 2181cfcaf428
- 1mo ago Changed · -24 lines · -1 tokens per session fba25ec7fa20
- 1mo ago First seen · 110 lines · 38 tokens per session scan A 8a65461beb43
do-it-architecture is a skill published in the GitHub repository tdwhere123/do-it (28 stars, last pushed 12d ago), licensed MIT. It adds 28 tokens to every session and 300 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-30.
Other skills, from other repositories
kirby-debugging-and-tracing
Diagnoses Kirby rendering/runtime issues using MCP runtime rendering, dump traces, and template/snippet/controller indexes. Use when outputs are wrong, errors occur, or tracing execution paths is required.
kirby-headless-api
Exposes Kirby content to headless clients using the API, KQL, and JSON representations. Use when building API endpoints, KQL queries, or headless frontends.
kirby-ide-support
Improves IDE autocomplete and static analysis in Kirby projects with PHPDoc hints and Kirby IDE helper generation. Use when types are missing or IDE support is degraded.
rn-feature-development
This skill should be used when building any new feature in a React Native or Expo app, or when the $rn-dev-agent:rn-feature-dev command runs. Triggers on "build a feature", "add X to the app", "implement Y", "create a new screen", "rn-feature-dev", "feature development", "build me X", "add a screen", "wire up this…
creating-actions
This skill should be used when the user asks to "create an action", "save this flow as an action", "make this replayable", "record a reusable action", "author a Maestro flow as an action", "add a login/setup action", or when a verified UI walk should be persisted under .rn-agent/actions/ so future sessions can replay…
kano-backlog
Prioritize and refine a GitHub Issues backlog with the Kano model — categorize every open issue as Must-be, Performance, Attractive, Indifferent, or Reverse, apply Kano + priority labels back to GitHub automatically, and recommend the single best next issue to pick up. Use this whenever the user wants to triage…