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/phuonghx/aim-cli/seo-fundamentalsnpx skills add phuonghx/aim-cli --skill seo-fundamentalsgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/seo-fundamentals)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/seo-fundamentals"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/seo-fundamentals.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 | $0.00074 | $0.00842 |
| Opus 5 | $0.00037 | $0.00421 |
| Sonnet 5 | $0.00015 | $0.00168 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
seo-fundamentals 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SEO Fundamentals
Earning search visibility comes down to trustworthy content served on a technically sound site -- and the patience to let it compound.
E-E-A-T: the quality lens
Google's raters judge content through four overlapping qualities:
- Experience -- evidence of first-hand use: real screenshots, original examples, lived detail.
- Expertise -- demonstrated command of the subject and relevant credentials.
- Authoritativeness -- recognition from others: links, citations, mentions in the field.
- Trustworthiness -- HTTPS, honest claims, accurate and verifiable information.
Core Web Vitals
| Metric | Target | What it measures |
|---|---|---|
| LCP | under 2.5s | Loading speed of the main content |
| INP | under 200ms | Responsiveness to user input |
| CLS | under 0.1 | Visual stability during load |
Technical foundations
Crawlability and indexing
- XML sitemap -- hands crawlers a map of your pages.
- robots.txt -- declares what bots may and may not fetch.
- Canonical tags -- consolidate duplicate or near-duplicate URLs.
- HTTPS -- a baseline trust and ranking signal.
Delivery
- Fast pages satisfy a Core Web Vital and keep users around.
- Mobile-friendliness is a ranking factor in its own right.
- Clean, readable URLs help both crawlers and people.
On-page content
The key elements
- Title tag -- ~50-60 characters, lead with the primary keyword.
- Meta description -- ~150-160 characters, written to earn the click.
- H1 -- one per page, carrying the main topic.
- H2-H6 -- a logical, nested outline.
- Image alt text -- descriptive and natural, never keyword-stuffed.
What makes content rank
- Depth -- cover the topic thoroughly enough to satisfy intent.
- Freshness -- revisit and update when things change.
- Originality -- add value that isn't already everywhere else.
- Readability -- clear prose beats dense filler.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 109 lines · 74 tokens per session scan A b7a2fe1a8801
seo-fundamentals is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 842 once invoked, about $0.0004 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-31.
Other skills, from other repositories
mulch-record-from-evidence
Turn the evidence of a finished work session — git commits, changed files, recently-touched seeds issues — into well-formed ml record invocations. Use at session close, when an agent has made changes worth preserving as mulch expertise but hasn't yet recorded them.
implement
End-to-end workflow for taking MCP work items from backlog to merged PR. Handles git branching, schema-driven planning, implementation, independent review, and PR creation. Composes spec-quality, review-quality, and schema-workflow skills into a single pipeline. Use when a user says "implement this", "work on this…
session-retrospective
Analyzes the current implementation run — evaluates schema effectiveness, delegation alignment, note quality, and plan-to-execution fit. Captures cross-session trends and proposes improvements when patterns repeat. Use after implementation runs, or when user says 'retrospective', 'session review', 'what did we learn'…
prepare-release
End-to-end release automation — reads commits since last tag, infers semver bump, drafts changelog, creates release PR, merges it, waits for CI green, tags, and monitors the Docker build to completion. Use when the user says: prepare release, cut a release, bump version, create release PR, ship a new version, tag a…
ralph
Launcher for the Ralph-style queue drain script — emits the right node ralph-loop.mjs invocation based on the user's filter and bounds. The actual loop runs as a Node script that spawns one claude -p --worktree per iteration; this skill is the configurator, not the loop. Use when a user says: drain the backlog, ralph…
adopt-project-scope
Migrates an already-populated, unscoped Task Orchestrator database in place to the project-scoping convention — creates a project anchor root, re-parents existing work trees under it, and writes rootId back to config.yaml. Use when a user says: adopt project scope, migrate this database to project scoping, make this…