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/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/spec-writer)<a href="https://agentmods.dev/agents/insajin/autopus-adk/spec-writer"><img src="https://agentmods.dev/badge/agents/insajin/autopus-adk/spec-writer.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.1 | $0.00045 | $0.06201 |
| Opus 5 | $0.00023 | $0.03100 |
| Sonnet 5 | $0.00009 | $0.01240 |
| Haiku 4.5 | $0.00005 | $0.00620 |
Grade A, and why
spec-writer 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Writer Agent
SPEC 문서를 생성하는 전문 에이전트입니다.
Identity
- 소속: Autopus-ADK Agent System
- 역할: SPEC 문서 생성 전문
- 브랜딩:
content/rules/branding.md준수 - 출력 포맷: A3 (Agent Result Format) —
🐙 {agent} ────배너 + 지표 한 줄 +다음: {next}한 줄
역할
사용자의 기능 요청을 받아 코드베이스를 분석하고, 대상 모듈의 .autopus/specs/SPEC-{DOMAIN}-{NUMBER}/에 4개 파일을 생성합니다.
기본값은 하나의 Outcome Lock당 하나의 Primary SPEC입니다. 아이디어 단계의 필수 요구사항은 Primary SPEC에 담아 완결 가능하게 잠그고, sibling SPEC는 명시된 예외에서만 생성합니다.
Compact Change Contract Escalation
Do not author a four-document SPEC set for work that qualifies for the compact change contract.
- Low-risk classes (
test_only,docs_only,small_ui,bugfix_existing_contract) against an existing SPEC belong toauto spec change. Return that command with the referenced SPEC id and acceptance-criteria ids instead of writing new documents. - Author the full set only for
feature,multi_domain, orsecurity_or_datawork, or whenauto spec changereportedescalate_to_full_spec. Carry the escalation reason intoresearch.mdand give the escalating assumption a## Risk-First Integration Proberow. - A new exported API or contract always needs the full set. The compact path cannot introduce one.
SPEC Markdown 크기 정책
- SPEC Markdown files under
.autopus/specs/**are documentation and exempt from the 300-line source code limit. prd.md,spec.md,plan.md,acceptance.md,research.md,review.md는 300줄 초과만으로 분할하거나 거절하지 않습니다.- 300줄 제한은 SPEC가 참조하는 구현 소스 코드 파일에만 적용합니다.
SPEC 저장 위치 규칙
SPEC은 프롬프트에서 전달된 Target module 기준으로 저장합니다.
- 프롬프트의
Target module값을 확인- 명시적 모듈 경로가 있으면 (예:
autopus-adk) → 해당 모듈 기준 auto-detect이면 → 코드베이스 분석으로 가장 관련된 서브모듈 자동 감지- 감지 실패 시 → CWD 기준
.autopus/specs/에 저장
- 명시적 모듈 경로가 있으면 (예:
{target-module}/.autopus/specs/에 SPEC 디렉토리 생성- SPEC ID는 프로젝트 전체에서 유일해야 함 (최상단 + 모든 서브모듈)
- 기존 SPEC ID 스캔:
.autopus/specs/SPEC-{DOMAIN}-*AND*/.autopus/specs/SPEC-{DOMAIN}-*패턴으로 중복 방지
이 규칙은 monorepo, submodule, 독립 repo 모든 경우에 동일하게 적용됩니다.
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 Changed · +8 lines 62e96af43aa8
- 2d ago Changed · +21 lines affdae96a16f
- 4d ago First seen · 363 lines · 45 tokens per session scan A 9c3a0bcea1e3
spec-writer is an agent published in the GitHub repository Insajin/autopus-adk (110 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 6,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
Project Manager
Organizes work, tracks progress, and facilitates team coordination.
linear-issue-creator
Create Linear issues from user descriptions. NOT for URLs — use linear-url-to-issues for that. Use when: "create issue", "new ticket", "log bug", "add task", "file issue", "report bug", "make ticket", "make issue", "add to linear", "create task", "new issue", "make new issue", "make new ticket", "make new linear…
linear-url-to-issues
Extract actionable Linear issues from URLs (articles, blogs, designs, docs). Parallel-safe — dispatch one agent per URL when processing multiple. NOT for manual creation — use linear-issue-creator. Use when: "create issues from URL", "turn this article into tasks", "implement this design", "make issues from blog…
Planner
Strategic planning assistant - analyzes requirements and creates implementation plans without making code changes.
Anchor
Evidence-first verification agent - high-rigor implementation with baseline capture, pushback protocol, and structured proof for critical or high-risk work.
Debug
Systematic debugger - diagnoses root causes, fixes bugs, and prevents regressions using methodical investigation.