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 plan-postgit 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/plan-post)<a href="https://agentmods.dev/skills/toktokhan-dev/agent-company/plan-post"><img src="https://agentmods.dev/badge/skills/toktokhan-dev/agent-company/plan-post/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/plan-post"><img src="https://agentmods.dev/badge/skills/toktokhan-dev/agent-company/plan-post.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.00002 | $0.00637 |
| Opus 5.5 | $0.00001 | $0.00255 |
| Sonnet 5.5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
plan-post 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 1mo 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
plan-post
1. 중복 확인
ls content/posts/
grep -l '<핵심 키워드>' content/posts/*.md
이미 다룬 주제면 새 글 대신 기존 글 갱신을 제안한다. 비슷한 글이 둘이면 둘 다 순위가 떨어진다.
2. 리서치
- 실제로 검색되는 질문 형태를 확인한다 ("~하는 법", "~와 ~의 차이").
- 답변 엔진에 같은 질문을 던져 지금 어떤 페이지가 인용되는지 본다. 그 페이지에 없는 것이 우리의 각이다.
- 검증 가능한 것만 다룬다. 출처를 못 찾을 주제는 잡지 않는다.
3. 아웃라인
헤딩만 읽어도 흐름이 보여야 한다. 각 섹션에 다룰 내용을 한 줄씩 적는다.
## 왜 파일 기반인가
- 에이전트에게 파일 IO가 네이티브, DB는 실패 지점을 늘림
## 트레이드오프
- 수천 개로 늘면 전체 스캔이 느려짐 → 인덱스 캐시 시점
질문형 헤딩을 섞는다. 답변 엔진의 Q&A 매칭에 유리하다.
4. 파일 생성
node --experimental-strip-types --no-warnings -e "
import('./packages/content/src/index.ts').then(m => {
const now = new Date().toISOString();
m.writePost({
title: '<제목>',
slug: '<kebab-case-slug>',
description: '<1~2문장>',
status: 'draft',
author: 'blog-writer',
createdAt: now, updatedAt: now,
category: '<카테고리>',
tags: ['<태그>'],
}, '<아웃라인 마크다운>');
});
"
content/posts/*.md를 에디터로 직접 만들지 말고 이 경로를 쓴다. 스키마 검증을 거쳐야 admin이 읽을 수 있다.
완료 조건
content/posts/<slug>.md생성됨,status: draft- 아웃라인의 각 섹션에 다룰 내용이 한 줄 이상
seo.keywords후보와geo.faq질문 후보를 사람에게 제시
하지 않을 것
- 본문을 쓰지 않는다. 다음 단계다.
- 검증하지 않은 수치를 아웃라인에 넣지 않는다.
- 아웃라인 승인 없이 3,000자를 쓰지 않는다. 방향을 잡는 비용은 여기서 가장 싸다.
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.
- 1mo ago First seen · 71 lines · 2 tokens per session scan A 1fd7bf4d5608
plan-post is a skill published in the GitHub repository TOKTOKHAN-DEV/agent-company (85 stars, last pushed 2mo ago), licensed MIT. It adds 2 tokens to every session and 637 once invoked, about $0.0000 per session on Opus 5.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
backlog
Seed a backlog from the project's documents: the Product Owner reads docs/ (plus the constitution and ROADMAP.md), proposes an ordered list of feature-sized items each traced to a source section, the user edits the list, and on explicit confirmation each item is filed as a GitHub issue that /story-time can import. Use…
backend-developer
Backend Developer (/be, alias: James, /james) - Senior Backend Developer with 10+ years experience. Covers Java/Spring Boot (default), Kotlin, Python/FastAPI, PHP/Laravel, Quarkus, and Kafka/messaging - detects the project's stack and loads the matching reference. Use when implementing server features, REST APIs…
java
Java language and JVM engineering standards — records and sealed-type modelling, JSpecify null-safety with NullAway as a build error, immutability, virtual threads and modern concurrency, Error Prone/ArchUnit/PIT build gates, JUnit 6 testing doctrine, and boundary security. Load whenever writing, refactoring, or…
sql
SQL and relational-database engineering with dialect branches for Postgres, MySQL, Oracle, and SQLite. Load whenever writing, editing, or reviewing SQL: a .sql file, a schema migration, a raw query embedded in application code, index/EXPLAIN/tuning work, or stored procedures/triggers. NOT for ORM entity mapping where…
typescript
JavaScript/TypeScript language engineering — the strictest-profile type system (discriminated unions, branded types, satisfies), parse-don't-validate boundaries with Zod, ESM and the Node runtime, typescript-eslint discipline (no floating promises), and Vitest/MSW/fast-check testing. Load whenever writing, editing, or…
product-owner
Product Owner (/po, alias: Max, /max) - Senior PO with 10+ years agile experience. Use when defining product vision, creating/prioritizing backlog, writing user stories with acceptance criteria, making scope decisions, validating features against business goals, or planning releases and sprints.