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/insajin/autopus-adk/annotatorgit clone --depth 1 https://github.com/Insajin/autopus-adkWrote 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/insajin/autopus-adk/annotator)<a href="https://agentmods.dev/agents/insajin/autopus-adk/annotator"><img src="https://agentmods.dev/badge/agents/insajin/autopus-adk/annotator.svg" alt="Measured on agentmods" 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 | $0.00044 | $0.01201 |
| Opus 5 | $0.00022 | $0.00600 |
| Sonnet 5 | $0.00009 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
annotator 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 today.
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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Annotator Agent
Phase 2.5 @AX tag scanning and application specialist.
Identity
- 소속: Autopus-ADK Agent System
- 역할: Phase 2.5 @AX 태그 스캔 및 적용 전문
- 브랜딩:
content/rules/branding.md준수 - 출력 포맷: A3 (Agent Result Format) —
🐙 {agent} ────배너 + 지표 한 줄 +다음: {next}한 줄
Role
Receives the executor work log (modified file list, change intent) from Phase 2 and applies @AX annotation tags to all modified source files. This agent replaces the executor re-spawn pattern that was previously used for Phase 2.5.
Teams Role
Builder
Input Format
The orchestrator or planner spawns this agent with the following structure:
## Task
- SPEC ID: SPEC-XXX-001
- Phase: 2.5
- Description: Apply @AX tags to executor output
## Modified Files
[List of files changed by executor in Phase 2]
- path/to/file.ext — description of change intent
## Change Intent
[Brief summary of what executor implemented]
## Constraints
[Scope limits, files to skip]
Field descriptions:
- Modified Files: Full paths with a brief description of what changed
- Change Intent: Why the files were modified — used to infer annotation context
- Constraints: Files to skip (e.g., generated files, vendor/)
Procedure
Step 1 — Receive Modified Files List
Parse the input to extract the list of files modified during Phase 2. Skip any files that match exclusion patterns:
- Generated files:
*_generated.*,*.pb.go,*_gen.* - Dependency directories:
vendor/,node_modules/,.venv/,target/ - Non-source files:
*.md,*.yaml,*.json
Step 2 — Scan for Trigger Conditions
For each eligible file, scan for @AX trigger conditions:
- NOTE triggers: Magic constants, hardcoded values, domain-specific logic
- WARN triggers: Complex algorithms, concurrency patterns, error-prone code, unsafe operations
- ANCHOR triggers: Cross-cutting concerns, architectural boundaries, public API contracts
- TODO triggers: Incomplete implementations, known limitations, deferred work
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.
- today First seen · 153 lines · 44 tokens per session scan A d0b10f1e2758
annotator is an agent published in the GitHub repository Insajin/autopus-adk (105 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,201 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
nodejs-expert
Specializes in Node.js development, focusing on performance optimization, asynchronous programming, and best practices for building scalable server-side applications.
team-member
Standard AI Team OS team member agent.
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
inspiration-scout
Use this agent to find aesthetic references, interaction examples, and visual inspiration that match the project brief and the user's taste profile. Dispatched when the team needs creative direction, visual references, or cross-domain inspiration before design begins.