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/techtankto/techtank-site/gitnpx skills add techtankto/techtank-site --skill gitgit clone --depth 1 https://github.com/techtankto/techtank-siteWhat 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.00732 |
| Opus 5 | $0.00029 | $0.00366 |
| Sonnet 5 | $0.00012 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
git 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git
How change is recorded.
Workflow
- Work on the branch defined for the task at hand. Never push directly to
main. - Create new commits rather than amending. Never force-push or skip hooks without explicit permission.
- Task PRs target their milestone branch; milestone PRs target the latest
main. Work outside a milestone stays on a feature branch and PRs only when explicitly asked.
Conventional Commits
-
All commit subjects follow Conventional Commits:
<type>(<optional scope>): <imperative summary>- Allowed types:
feat,fix,docs,style,refactor,perf,test,build,ci,chore,revert. - Scopes match the affected area: the surface (
home), the layer (templates,tokens,constants), or the docs (prd,docs). Omit when global. - Subject: ≤ 72 characters, lowercase, no trailing period.
- Body: explain the why when the diff alone doesn't.
- Breaking changes:
!suffix and aBREAKING CHANGE:footer for route moves, renames, or behavior changes.
- Allowed types:
Branch naming
-
Branches follow the same type vocabulary as commits:
<type>/<short-kebab-summary>- ≤ 40 characters, lowercase, hyphen-separated.
- Milestone and task branches carry their identifiers:
feat/m02-works,feat/m02-t04-works-ledger. - Branches outside a milestone reference the affected area:
fix/date-zoning,docs/initial-plan.
Attribution
- No AI/agent attribution in commits, PRs, or issues: no
Co-Authored-By: Claude/Codex, no "Generated with Claude Code" markers, noclaude.ai/codesession links.
Review
- Read the project's own vendored skills before reviewing the diff. Skills under
.claude/skills//.agents/skills/are that project's actual, current standards, not generic advice; load the ones relevant to the changed files (componentsfor a component diff,datafor a constants/data change,nextjsfor routing, etc.) and check the diff against what they specifically say before reaching for anything else. - Then apply conventional best practice: correctness, security, performance, test coverage, readability — the concerns a project's skills don't cover because they're universal rather than project-specific.
- A skill deviation is a finding on its own, distinct from a generic style nit: name the skill and the rule it violates, not just "this looks off."
- When a project has no vendored skills, or the change touches an area none of them cover, fall back to conventional best practice alone — don't invent a project standard that isn't written down anywhere.
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 · 63 lines · 58 tokens per session scan A 105e4351399d
git is a skill published in the GitHub repository techtankto/techtank-site (5 stars, last pushed 6d ago), licensed MIT. It adds 58 tokens to every session and 732 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.