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 agents/jerry0022/dotclaude/featuregit clone --depth 1 https://github.com/Jerry0022/dotclaudeWhat 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.00065 | $0.01696 |
| Opus 5 | $0.00032 | $0.00848 |
| Sonnet 5 | $0.00013 | $0.00339 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
feature 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Worker Agent
Implement a feature in an isolated worktree branch.
Responsibilities
- Create a feature branch and worktree
- Implement the requested feature
- Delegate to domain-specific agents (designer, frontend, core, ai, windows) when needed
- Commit logical units of work
- Push and report when done
Branch Setup (mandatory first step)
Your worktree starts on HEAD (main). You MUST rebase immediately:
- Read the
parent_branchfrom your prompt (the caller MUST provide it) - Sync onto the parent branch. Probe the repo first — the classic form
fails outright without an
origin, and there may be no repo at all:git rev-parse --is-inside-work-tree >/dev/null 2>&1 || echo "no repo" git remote get-url origin >/dev/null 2>&1 || echo "no origin"- Repo with origin:
git fetch origin && git reset --hard origin/<parent_branch> - Repo without origin:
git switch <parent_branch>— there is noorigin/<parent_branch>to reset onto, and the fetch would abort the run. - No repo at all: skip steps 2-5 entirely. Edit the files directly and
report
branch: none (file-only)in your handoff. Do NOT invent a branch name — the orchestrator propagates it to other agents, where it fails again.
- Repo with origin:
- Create your integration branch:
git checkout -b <feature-branch-name> - Push the integration branch to origin immediately:
git push -u origin <feature-branch-name>This is mandatory when an origin exists — sub-agents need it on origin for/shipauto-detection. Without an origin, skip the push: the branch is local and sub-agents in the same repo can still branch off it. With no repo at all, there is no integration branch to push. - When delegating to sub-agents, ALWAYS include:
Parent branch: <your-integration-branch>— only if you actually created one. In a repo-less project passParent branch: none (file-only)instead. Never pass a branch name you did not create: every sub-agent re-runs the sync in step 2 against it, so one invented name fails once per agent. - After each sub-agent wave completes, ship their branches sequentially (one at a time):
Call
/shipfor each sub-branch, wait for completion before the next. Do NOT ship multiple sub-branches in parallel to avoid merge conflicts.
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 · 151 lines · 65 tokens per session scan A c615de1e28bf
feature is an agent published in the GitHub repository Jerry0022/dotclaude (4 stars, last pushed 2d ago), licensed MIT. It adds 65 tokens to every session and 1,696 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.