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 skills/toktokhan-dev/agent-company/write-specnpx skills add TOKTOKHAN-DEV/agent-company --skill write-specgit clone --depth 1 https://github.com/TOKTOKHAN-DEV/agent-companyWrote 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/skills/toktokhan-dev/agent-company/write-spec)<a href="https://agentmods.dev/skills/toktokhan-dev/agent-company/write-spec"><img src="https://agentmods.dev/badge/skills/toktokhan-dev/agent-company/write-spec.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.00002 | $0.00627 |
| Opus 5 | $0.00001 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
write-spec 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 6d 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
write-spec
1. 중복과 충돌을 먼저 본다
ls specs/
grep -ril "<핵심 키워드>" specs/
같은 흐름을 이미 정해 둔 명세가 있으면 새로 쓰지 말고 그쪽을 고친다. 화면 경로가 겹치면
apps/miniapp/src/App.tsx 의 routes 와 대조한다.
2. 템플릿을 복사한다
cp specs/_template.md specs/<기능-kebab>.md
파일명은 kebab-case. 한글도 허용된다 (포인트-적립.md). 밑줄로 시작하는 파일은 preflight 의
검사 대상이 아니므로 실제 명세에는 쓰지 않는다.
3. 화면 표를 먼저 채운다
경로 → 이름 → 역할. 경로는 해시 라우팅 기준(/, /points)이다.
각 화면마다 진입 · 이탈 · 빈 상태 · 로딩 · 실패 다섯 가지를 적는다. 이 중 하나라도
비어 있으면 ui-builder 가 임의로 정하게 된다.
4. 수용 기준을 쓴다
체크박스로. 각 문장은 앱을 켜고 확인할 수 있어야 한다.
최소한 이 네 개는 거의 모든 기능에 해당한다:
- 첫 화면에서 뒤로가기를 누르면 미니앱이 닫힌다
- 모든 화면에 빠져나갈 방법이 있다
- 앱을 재시작해도 <무엇>이 유지된다
- 모든 인터랙션이 2초 안에 반응한다
5. 심사 항목을 옮겨 적는다
wiki/04-review-checklist.md 에서 이 기능이 건드리는 항목만 골라 「심사 관련」에 넣는다.
전부 복사하지 않는다 — 해당 없는 항목이 섞이면 아무도 안 읽는다.
6. 범위 밖과 열린 질문
범위 밖을 반드시 적는다. 적지 않으면 구현 중에 늘어난다.
열린 질문이 하나라도 있으면 구현으로 넘기지 않는다. 사람에게 묻고 답을 받아 명세에 반영한 뒤 넘긴다.
완료 확인
pnpm preflight
specs 규칙에 error 가 없어야 한다.
출력
- 만든 파일 경로
- 정한 것 (화면 수, 핵심 수용 기준)
- 사람에게 묻는 것 (열린 질문)
- 다음 단계:
pnpm agent ui-builder "<화면 이름>"
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.
- 6d ago First seen · 72 lines · 2 tokens per session scan A b23b45259535
write-spec is a skill published in the GitHub repository TOKTOKHAN-DEV/agent-company (75 stars, last pushed 9d ago), licensed MIT. It adds 2 tokens to every session and 627 once invoked, about $0.0000 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 skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.