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 skills add TOKTOKHAN-DEV/agent-company --skill review-and-submitgit 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/review-and-submit)<a href="https://agentmods.dev/skills/toktokhan-dev/agent-company/review-and-submit"><img src="https://agentmods.dev/badge/skills/toktokhan-dev/agent-company/review-and-submit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/toktokhan-dev/agent-company/review-and-submit"><img src="https://agentmods.dev/badge/skills/toktokhan-dev/agent-company/review-and-submit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00003 | $0.00692 |
| Opus 5 | $0.00002 | $0.00346 |
| Sonnet 5 | $0.00001 | $0.00138 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
review-and-submit 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 11d 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
review-and-submit
절대 규칙
status를 published로 바꾸지 않는다. 당신의 종착점은 in_review다.
자기가 쓴 글을 자기가 발행하면 이 템플릿의 검수 게이트가 무의미해진다.
1. 자동 감사
pnpm audit:content <slug>
admin /review/<slug>와 같은 함수를 쓰므로 사람이 볼 결과와 항상 일치한다.
error가 하나라도 있으면 해당 단계로 돌아가 고친다. 넘기지 않는다.
2. 사실 확인
<!-- TODO: 확인 필요 -->를 전부 해소한다. 하나라도 남으면 미완성이다.- 수치·버전·벤치마크를 1차 출처와 대조한다.
- 확인이 안 되면 그 문장을 뺀다. 애매하게 남기지 않는다.
3. 가이드라인 대조
wiki/03-content-guidelines.md를 항목별로 확인한다. 특히 자주 어기는 것:
- 과장 형용사
- 요약 반복 마무리
- 벽처럼 긴 문단
- 언어 태그 없는 코드 블록
4. 이미지 출처 감사
cover가 있으면:
source가codex-imagegen인데origin에 프롬프트가 없으면 의심한다.image-maker에 확인한다.web-search인데license가 없으면 error다. 발행이 막힌다.alt가 비어 있으면 error다.
5. 링크 확인
- 내부 링크가 실재하는 슬러그를 가리키는지
- 외부 링크가 살아 있는지
6. 검수 기록
review.checks의 6개 항목을 채운다. 확인하지 않은 항목의 체크박스를 켜지 않는다.
남은 warn 각각에 대해 왜 남겨두는지 review.notes에 적는다.
7. 제출
status: in_review로 바꾸고 사람에게 넘긴다.
완료 조건
pnpm audit:content <slug>error 0개- TODO 표시 0개
review.checks실제 확인 후 기록status: in_review
보고 형식
슬러그: nextjs-16-cache-components
감사 점수: 93 (error 0 · warn 2)
남은 warn: geo.citations — 1차 출처 2건뿐, 벤더 문서 위주라 남겨둠
body — 2,100자, 권장 범위 하단
검수 링크: http://localhost:3001/review/nextjs-16-cache-components
발행 버튼은 검수 화면에서 직접 눌러 주세요.
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.
- 11d ago First seen · 78 lines · 3 tokens per session scan A 188fe959debe
review-and-submit is a skill published in the GitHub repository TOKTOKHAN-DEV/agent-company (77 stars, last pushed 15d ago), licensed MIT. It adds 3 tokens to every session and 692 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
capture-lessons
Ship and capture lessons workflow. Creates the PR, updates lessons learned, updates documentation, generates the sprint retrospective, and updates the backlog. Use at the end of a sprint cycle, or when the user says "ship", "capture", "lessons", "retro", "retrospective", "wrap up", or "done with this sprint". Also use…
red-team
Security red team that produces executable attack scripts and a static code audit. Use this skill for any security sprint, pre-release hardening, or when code touches authentication, billing, data storage, API endpoints, or secrets. Also use when the user says "red team", "pentest", "attack surface", "security audit"…
full-sprint
Orchestrates a complete sprint cycle autonomously. Each phase runs as a separate claude -p session for context isolation. Use when the sprint-directive.md is ready and the sprint should execute end-to-end. Also use when the user says "run a full sprint", "execute the sprint", "build everything", "autonomous sprint"…
data-analysis
Fetch, query, and analyze project data. Use this skill when the user wants to investigate metrics, understand user behavior, debug a data issue, or answer a question that requires looking at real data. Triggers on "what happened", "why did X drop", "show me the numbers", "query", "metrics", "funnel", "cohort", "data"…
fix
Fix phase workflow. Fixes issues identified during code review, based on the triaged review output. Use after a review phase is complete and the human has triaged the findings, or when the user says "fix", "fix the issues", "address review feedback", or "apply fixes". Also use when the user says "fix these" after…
review
Code review workflow. Reviews the build output for quality, conventions, performance, security, and test coverage. Use after a build phase is complete, or when the user says "review", "check the code", "PR review", "quality check", or "is this good". Also use when the user wants a second opinion on code that was just…