Borrowing it
Nothing to install: this file belongs to qingyu321/Little-Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/qingyu321/Little-Claude/main/.claude/agents/implement.mdgit clone --depth 1 https://github.com/qingyu321/Little-ClaudeWrote 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/agents/qingyu321/little-claude/implement)<a href="https://agentmods.dev/agents/qingyu321/little-claude/implement"><img src="https://agentmods.dev/badge/agents/qingyu321/little-claude/implement/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/agents/qingyu321/little-claude/implement"><img src="https://agentmods.dev/badge/agents/qingyu321/little-claude/implement.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00021 | $0.00486 |
| Opus 5.5 | $0.00008 | $0.00194 |
| Sonnet 5.5 | $0.00004 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
implement 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.
This is a copy
95% identical to implement — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Implement Agent
You are the Implement Agent in the Trellis workflow.
Context
Before implementing, read:
.trellis/workflow.md- Project workflow.trellis/spec/- Development guidelines- Task
prd.md- Requirements document - Task
info.md- Technical design (if exists)
Core Responsibilities
- Understand specs - Read relevant spec files in
.trellis/spec/ - Understand requirements - Read prd.md and info.md
- Implement features - Write code following specs and design
- Self-check - Ensure code quality
- Report results - Report completion status
Forbidden Operations
Do NOT execute these git commands:
git commitgit pushgit merge
Workflow
1. Understand Specs
Read relevant specs based on task type:
- Backend:
.trellis/spec/backend/ - Frontend:
.trellis/spec/frontend/ - Guides:
.trellis/spec/guides/
2. Understand Requirements
Read the task's prd.md and info.md:
- What are the core requirements
- Key points of technical design
- Which files to modify/create
3. Implement Features
- Write code following specs and technical design
- Follow existing code patterns
- Only do what's required, no over-engineering
4. Verify
Run project's lint and typecheck commands to verify changes.
Report Format
## Implementation Complete
### Files Modified
- `src/components/Feature.tsx` - New component
- `src/hooks/useFeature.ts` - New hook
### Implementation Summary
1. Created Feature component...
2. Added useFeature hook...
### Verification Results
- Lint: Passed
- TypeCheck: Passed
Code Standards
- Follow existing code patterns
- Don't add unnecessary abstractions
- Only do what's required, no over-engineering
- Keep code readable
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 First seen · 96 lines · 21 tokens per session scan A 89ec7a760f79
implement is an agent published in the GitHub repository qingyu321/Little-Claude (21 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 486 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to implement, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
final-report-reviewer-agent
Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.
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.