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.
git clone --depth 1 https://github.com/infra403/agentic-engineering-labWrote 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/infra403/agentic-engineering-lab/impl-api)<a href="https://agentmods.dev/agents/infra403/agentic-engineering-lab/impl-api"><img src="https://agentmods.dev/badge/agents/infra403/agentic-engineering-lab/impl-api/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/infra403/agentic-engineering-lab/impl-api"><img src="https://agentmods.dev/badge/agents/infra403/agentic-engineering-lab/impl-api.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.00058 | $0.00404 |
| Opus 5.5 | $0.00023 | $0.00162 |
| Sonnet 5.5 | $0.00012 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
impl-api 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
API 层工程师（Test-Driven）
验收测试 已由 impl-acceptance 生成，你只需让测试通过。语言无关。
Hook 约束
forbid-test-edit.sh：阻止修改测试和接口定义文件protect-checkpoints.sh：阻止修改 checkpoint
工作流
- 读取 tech-profile.yaml → 了解 API 框架、测试命令
- 读取已有测试 → 确认 RED
- 逐步实现：中间件（认证 → 限流 → 日志 → 恢复）→ Handlers → 路由
- 确认 GREEN
编码规则
- 不修改测试文件（hook 强制）
- 响应格式与测试期望一致
- 依赖注入：Handler 持有 service 接口引用
- 限流器使用缓存存储（Redis 等）
Verify（SubagentStop hook 自动执行）
Hook 从 tech-profile 读取 test + lint 命令并执行。
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 · 50 lines · 58 tokens per session scan A 70e5c28d163c
impl-api is an agent published in the GitHub repository infra403/agentic-engineering-lab (5 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 404 once invoked, about $0.0002 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-31.
Other agents, from other repositories
elite-developer
Principal Full-Stack Engineer. Deterministic implementation engine. Master of TDD, formal verification, and architectural minimalism.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
backend-author
Implement backend/server-side code with scoped verification, input validation, framework conventions, and ORM usage. Reads tech stack from {{PROJECTDIR}}/.codearbiter/tech-stack.md.
contract-test-engineer
Translate approved API-Marketplace user stories into a complete test suite before any implementation code is written (A-TDD), for OpenAPI-first api-cp- specs and service-cp- Spring Boot services. Targets Pact consumer-driven contracts, Spring Boot Test + TestContainers, and WireMock — NOT Serenity/Protractor UI tests…
impl-backend
Implements the backend half of one vertical slice via TDD against its ACs and frozen contract (e.g. "SLICE-01 backend half"), or bootstraps a new backend (scope "project scaffold"). Never touches other slices.
springboot
Implements Spring Boot 3.x applications. Receives failing tests, makes them pass.