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/plan-postnpx 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.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.00637 |
| Opus 5 | $0.00001 | $0.00318 |
| Sonnet 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 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
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.
- 6d 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 (75 stars, last pushed 9d ago), licensed MIT. It adds 2 tokens to every session and 637 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.