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/leeyudok/agents-scaffold/readmegit clone --depth 1 https://github.com/LeeYudok/agents-scaffoldWrote 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/leeyudok/agents-scaffold/readme)<a href="https://agentmods.dev/agents/leeyudok/agents-scaffold/readme"><img src="https://agentmods.dev/badge/agents/leeyudok/agents-scaffold/readme.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.00000 | $0.00290 |
| Opus 5 | $0.00000 | $0.00145 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
README 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 4d 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
agents/ — AI 팀원 (서브에이전트 정의)
작업 특화 서브에이전트. 각 에이전트 = 마크다운 1파일. frontmatter:
| 필드 | 용도 |
|---|---|
name |
에이전트 이름 |
description |
언제 위임할지(자동 선택 기준) |
tools |
접근 가능 도구(쉼표 구분) |
model |
sonnet/opus/haiku/inherit(부모 세션 상속) 또는 전체 모델 ID. 작업 강도별 차등 — 기계적 스캔·대량 반복=haiku, 일반 구현·리뷰=sonnet, 심층 판단·보안=opus |
memory |
user/project/local — 세션 간 컨텍스트 학습 |
maxTurns |
중단 전 최대 턴 |
신규 생성 시 {{PROJECT_NAME}}-ag-* prefix 권장. 동봉 예시: code-reviewer.md.
Workflow 스크립트에서 에이전트를 부를 땐 model 외에 effort(low~max)로도 강도를
조절할 수 있다 — workflows/README.md 참조.
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.
- 4d ago First seen · 18 lines · 0 tokens per session scan A fa1bc32bc633
README is an agent published in the GitHub repository LeeYudok/agents-scaffold (25 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 290 tokens. 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
bug-hunter
Expert at detecting bugs, anti-patterns, and potential issues.
code-reviewer
Expert code reviewer for quality and maintainability.
security-auditor
Security expert for vulnerability detection and remediation.
test-engineer
Specialized agent for comprehensive test generation.
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.