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 optimize-seo-geogit 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/optimize-seo-geo)<a href="https://agentmods.dev/skills/toktokhan-dev/agent-company/optimize-seo-geo"><img src="https://agentmods.dev/badge/skills/toktokhan-dev/agent-company/optimize-seo-geo/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/optimize-seo-geo"><img src="https://agentmods.dev/badge/skills/toktokhan-dev/agent-company/optimize-seo-geo.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.00006 | $0.00629 |
| Opus 5 | $0.00003 | $0.00315 |
| Sonnet 5 | $0.00001 | $0.00126 |
| Haiku 4.5 | $0.00001 | $0.00063 |
Grade A, and why
optimize-seo-geo 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
optimize-seo-geo
먼저
wiki/04-seo-geo-playbook.md를 읽는다. SEO와 GEO는 다른 게임이다 — 전자는 순위, 후자는 인용.
SEO
| 필드 | 규칙 |
|---|---|
seo.title |
≤60자. 비우면 title이 쓰인다 |
seo.description |
≤160자. 검색 결과에 그대로 노출된다고 생각하고 쓴다 |
seo.keywords |
3~6개. 주 키워드 하나에 집중 |
seo.canonical |
다른 곳에도 실린 글이면 원본 URL |
seo.ogImage |
비우면 cover.src가 쓰인다 |
키워드를 억지로 늘리지 않는다. 관련 없는 키워드는 순위를 오히려 해친다.
GEO
| 필드 | 규칙 |
|---|---|
geo.answerSummary |
답변 엔진이 통째로 인용할 2~3문장. 결론부터. |
geo.faq |
최소 2쌍. 실제로 검색되는 질문 형태로 |
geo.entities |
이 글이 연결되어야 할 고유명사 (제품·기술·회사명) |
geo.citations |
본문이 인용한 1차 출처 |
geo.locale / targetMarkets |
지역 타깃팅 |
faq는 FAQPage JSON-LD로, answerSummary는 페이지 상단 요약 블록으로 렌더링된다.
원칙
요약은 추출이지 창작이 아니다. 본문에 없는 내용을 answerSummary에 넣지 않는다.
FAQ 답변도 본문에서 근거를 찾을 수 있어야 한다. 근거가 없으면 FAQ를 만들지 말고 본문을 보강해야 한다고
보고한다.
검증
pnpm audit:content <slug>
[seo]와 [geo] lane에 error가 없어야 한다.
git diff content/posts/<slug>.md
본문에 diff가 있으면 안 된다. 있으면 되돌린다.
완료 조건
- SEO/GEO lane error 0개
geo.faq2쌍 이상,geo.answerSummary존재- 본문 diff 없음
하지 않을 것
- 본문을 수정하지 않는다. 문제가 있으면 write-draft로 돌아간다.
status를 바꾸지 않는다.- 검증하지 않은 URL을
citations에 넣지 않는다.
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 · 68 lines · 6 tokens per session scan A 765009ddb0c9
optimize-seo-geo is a skill published in the GitHub repository TOKTOKHAN-DEV/agent-company (77 stars, last pushed 14d ago), licensed MIT. It adds 6 tokens to every session and 629 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…