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/tdwhere123/do-it/do-it-contextnpx skills add tdwhere123/do-it --skill do-it-contextgit clone --depth 1 https://github.com/tdwhere123/do-itWhat 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.00051 | $0.02358 |
| Opus 5 | $0.00026 | $0.01179 |
| Sonnet 5 | $0.00010 | $0.00472 |
| Haiku 4.5 | $0.00005 | $0.00236 |
Grade A, and why
do-it-context 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 2d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Do-It Context
Purpose
.do-it/CONTEXT.md is the single canonical place where this project's terminology, invariants, and relationship-shapes live for AI workflows. Other skills (especially do-it-decide, do-it-review, do-it-code-quality) read it before debating definitions. This skill also owns the deeper domain-language pass (canonical glossary + contradiction checks) — see § Domain Glossary Mode.
It is not a wiki, README replacement, or onboarding doc. It is a terse, declarative artifact intended to fit in the AI's working memory budget. Keep it under ~200 lines.
When To Use
- The first time
do-it-decideclarifies a term in this repo, write it back here so the next session does not re-litigate. - When a constraint surfaces that the codebase will not enforce on its own (e.g. "user IDs are global, never per-tenant"), record it here.
- When two terms turn out to mean the same thing, pick one and put it here so the alias is killed at the source.
- When a relationship has cardinality that matters (1:1, 1:N, N:M with constraint), record the cardinality.
When NOT To Use
- Onboarding narrative, history, or rationale → that belongs in
README.md/docs// commit messages. - Tutorial content → README.
- Anything code can express clearly on its own → leave it in code.
- Status / TODO / current-work →
.do-it/plans/or the issue tracker.
Context Hierarchy
When context sources disagree, use this order:
- Current code, tests, schemas, manifests, generated source-of-truth scripts, and live command output.
CLAUDE.md(or the host's equivalent root agent-instruction file) for durable, human-authored conventions and behavioral rules the team chose — authoritative for how to work here, though current code still wins on what the code is..do-it/CONTEXT.mdfor terse repo terms, invariants, and relationships that code does not express accessibly.- Current plan, grill log, task card, or issue for the active work.
- README, docs, ADRs, and maintenance guides.
- Memory, old reports, previous worker summaries, and external sources.
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.
- 2d ago First seen · 220 lines · 51 tokens per session scan A 0b3d5b1703c4
do-it-context is a skill published in the GitHub repository tdwhere123/do-it (27 stars, last pushed 20d ago), licensed MIT. It adds 51 tokens to every session and 2,358 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
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-code-review-swarm
Agent skill for code-review-swarm - invoke with $agent-code-review-swarm.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-repo-architect
Agent skill for repo-architect - invoke with $agent-repo-architect.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.