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 humanerd-drew/opencode-drewgent --skill seo-servicegit clone --depth 1 https://github.com/humanerd-drew/opencode-drewgentWrote 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/humanerd-drew/opencode-drewgent/seo-service)<a href="https://agentmods.dev/skills/humanerd-drew/opencode-drewgent/seo-service"><img src="https://agentmods.dev/badge/skills/humanerd-drew/opencode-drewgent/seo-service.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.00000 | $0.00625 |
| Opus 5 | $0.00000 | $0.00313 |
| Sonnet 5 | $0.00000 | $0.00125 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
seo-service 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 3d 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
SEO Service
What
RSS로 수집된 2,853+ SEO 기사를 지식베이스로 삼아 사용자의 블로그 콘텐츠를 지속적으로 진단/수정/관리하는 SaaS.
Differentiation
- 살아있는 규칙 — Google 업데이트 RSS가 들어오면 규칙이 자동 업데이트되고, 기존 글을 재진단
- 자동 수정 — meta/h1/alt/heading 등 기계적 문제는 플러그인이 직접 수정 (Fix It 버튼)
- 선제 알림 — 사용자가 모르는 Google 업데이트의 영향을 먼저 알려줌
Architecture
[RSS harvester] → rules.yaml (수동 → 점진적 자동화)
↓
[진단 엔진] → crawl URL → rule check → 문제 리스트
↓
[SaaS] → 회원/결제/도메인관리/D1
↓
[WordPress plugin] → REST API로 글 읽기/쓰기
↓
[알림] → Discord webhook / email
Phase 0: Product Rules (초기 30개)
engine/rules/*.ts에 저장. 각 규칙은:
- id, name, category, severity, description
- check(url, html): Promise<Pass|Fail[]>
- autoFix? 가능한 경우 fix 함수
Code Layout
~/seo-service/
worker.ts # CF entry + routing
wrangler.jsonc
src/
engine/
crawler.ts # URL crawl + HTML parse
rules/ # *.ts — rule 하나당 파일 하나
engine.ts # runAllRules(url) → 결과[]
reports/
schemas/ # ReportSchema 구현
controllers/
auth.ts # 로그인/회원가입
sites.ts # 도메인 등록/관리
audit.ts # 진단 실행/결과
payment.ts # PortOne 결제 (m-log 카피)
utils/
llm.ts # DeepSeek + NVIDIA fallback
crypto.ts # HMAC session
db/
queries.ts
migrations/
frontend/
app/
index.html
js/
core/ (Router, Component)
views/ (Login, Dashboard, SiteDetail, AuditResult)
components/
extension/
wordpress/
chrome/
Related
- SEO articles:
[[@memory/knowledge/seo-articles]] - Product plan:
[[@memory/growth/seo/seo-service/product-plan]]
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.
- 3d ago First seen · 75 lines · 0 tokens per session scan A 2749383012e7
seo-service is a skill published in the GitHub repository humanerd-drew/opencode-drewgent (2 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 625 tokens. 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…