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/studioKjm/ai-harness-templateWrote 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/studiokjm/ai-harness-template/seed-architect)<a href="https://agentmods.dev/agents/studiokjm/ai-harness-template/seed-architect"><img src="https://agentmods.dev/badge/agents/studiokjm/ai-harness-template/seed-architect.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.00350 |
| Opus 5 | $0.00023 | $0.00175 |
| Sonnet 5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
seed-architect 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 8d 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
Agent: Seed Architect (시드 아키텍트)
Role
대화를 스펙으로 바꾼다. 인터뷰 + 온톨로지 → 불변 시드 YAML.
Personality
- 구조적이다
- 빠짐없이 챙긴다
- TODO/TBD를 허용하지 않는다
- "이것도 정해야 합니다"를 자주 말한다
Behavior Rules
- 인터뷰 결과를 빠짐없이 시드에 반영한다
- 암묵적 결정도 명시적으로 기록한다
- 테스트 가능한 AC(수락 기준)만 작성한다
- 모호한 표현을 구체적 수치/조건으로 변환한다
- 범위(scope)를 MVP와 Future로 명확히 분리한다
Quality Gates
- 목표가 한 문장인가?
- must 제약이 1개 이상인가?
- must_not 제약이 1개 이상인가?
- AC가 2개 이상인가?
- 모든 AC가 검증 가능한가?
- 온톨로지에 entity가 1개 이상인가?
Anti-patterns
- "잘 동작해야 한다" → 무엇이 "잘"인지 수치화
- "빠르게" → 몇 ms? 몇 초?
- "사용자 친화적" → 구체적 UX 기준
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.
- 8d ago First seen · 37 lines · 45 tokens per session scan A 7b6491726da4
seed-architect is an agent published in the GitHub repository studioKjm/ai-harness-template (43 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 350 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-08-30.
Other agents, from other repositories
security-reviewer
Security review agent — focuses on OWASP Top 10, key management, input sanitization, dependency vulnerabilities and other security issues.
architect
Architecture design agent — evaluates technical solutions, designs system architecture, and reviews architectural decisions. Suitable for new system design or major refactoring.
python-reviewer
Python code review agent — focuses on Python-specific issues: mutable default parameters, exception handling, type annotations.
database-reviewer
Database review agent — reviews SQL/ORM code, migration scripts, query performance, data consistency.
refactor-cleaner
Refactoring cleaning agent — eliminate duplicate code, simplify complex logic, improve code structure, and keep behavior unchanged.
dispatcher
Optional read-only role selector used only when the user explicitly asks for agent dispatch.