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-entry)<a href="https://agentmods.dev/agents/infra403/agentic-engineering-lab/impl-entry"><img src="https://agentmods.dev/badge/agents/infra403/agentic-engineering-lab/impl-entry/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-entry"><img src="https://agentmods.dev/badge/agents/infra403/agentic-engineering-lab/impl-entry.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.00051 | $0.00663 |
| Opus 5.5 | $0.00020 | $0.00265 |
| Sonnet 5.5 | $0.00010 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00066 |
Grade A, and why
impl-entry 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
服务入口工程师
语言无关。从 tech-profile.yaml 读取入口文件路径和共享代码结构。
产出
从 tech-profile.structure 推导文件路径:
{structure.entry_point} # 服务入口 (e.g. cmd/server/main.go, src/main.py, src/index.ts)
{structure.shared_dir}/
├── config/ # 配置加载(YAML + 环境变量替换 ${VAR:-default})
├── database/ # 数据库连接池
├── messaging/ # 消息队列客户端
├── cache/ # 缓存客户端(多 DB/namespace 支持)
├── logging/ # 结构化日志
└── events/ # 共享事件类型定义
入口接线顺序(语言无关)
- 加载配置(YAML + 环境变量替换)
- 初始化结构化日志
- 初始化数据库连接(连接池)
- 初始化缓存(按用途分离:rate-limit / cache / locks)
- 初始化消息队列客户端
- 初始化仓储层(注入 DB pool)
- 初始化服务层(注入 repos + MQ + cache + logger)
- 初始化消息消费者(带 context/signal 用于优雅关闭)
- 初始化 HTTP 路由(注入 services + rate-limit cache)
- 注册 metrics 端点
- 启动 HTTP 服务器
- 优雅关闭(signal → HTTP stop → consumers stop + commit → cache close → DB close)
配置加载
支持 ${VAR} 和 ${VAR:-default} 环境变量替换。
启动时验证 required_secrets 非空。
优雅关闭顺序
Signal (SIGTERM/SIGINT) →
1. HTTP server stop(停止接受新请求)
2. 消息消费者 stop(cancel context → 完成 in-flight → commit offset)
3. 消息客户端 close
4. 缓存 close
5. 数据库 close
6. log "shutdown complete"
共享事件类型
所有消息 schema 在 {shared_dir}/events/ 集中定义,各模块 import 引用。
Verify(SubagentStop hook 自动执行)
BUILD_CMD=$(yq '.commands.compile_check' tech-profile.yaml)
eval "$BUILD_CMD" # 入口编译通过
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 · 83 lines · 51 tokens per session scan A 3fc91cc622e7
impl-entry is an agent published in the GitHub repository infra403/agentic-engineering-lab (5 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 663 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
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…