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.5 | $0.00002 | $0.00252 |
| Sonnet 5.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 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
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.
- 1mo 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 (85 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 629 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.