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 ZensInk/zens-ink-seo-package --skill rank-trackinggit clone --depth 1 https://github.com/ZensInk/zens-ink-seo-packageWrote 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/zensink/zens-ink-seo-package/rank-tracking)<a href="https://agentmods.dev/skills/zensink/zens-ink-seo-package/rank-tracking"><img src="https://agentmods.dev/badge/skills/zensink/zens-ink-seo-package/rank-tracking/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/zensink/zens-ink-seo-package/rank-tracking"><img src="https://agentmods.dev/badge/skills/zensink/zens-ink-seo-package/rank-tracking.svg" alt="Reviewed on agentmods" width="80" 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.00093 | $0.00806 |
| Opus 5.5 | $0.00037 | $0.00322 |
| Sonnet 5.5 | $0.00019 | $0.00161 |
| Haiku 4.5 | $0.00009 | $0.00081 |
Grade A, and why
rank-tracking 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 2d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rankings, GSC performance, DR
Three data legs: rank snapshots over time (SQLite), GSC ground truth, and DR lookups for sizing up any domain.
When to use
- "Track these 10 keywords weekly"
- "What queries actually bring me clicks?" (GSC)
- "What's the DR of these 5 domains?"
When NOT to use
- Daily rank checks on a big keyword set — rank checks cost SERP quota; weekly cadence is the intended rhythm.
Setup
pip install zens-ink
python3 -m zens_ink.setup_gsc # one-time GSC auth (for search_performance)
Keys in .env: SERPER_API_KEY (rank checks), GSC_* (Search Console),
AHREFS_API_KEY (DR lookups — free public API).
Commands
# Rankings with history
python3 -m zens_ink.rank_tracker add "open source seo tools,seo cli tool"
python3 -m zens_ink.rank_tracker check # snapshot now
python3 -m zens_ink.rank_tracker trend # latest vs previous
python3 -m zens_ink.rank_tracker history "seo cli tool"
# GSC performance (real data, read-only)
python3 -m zens_ink.search_performance --queries --limit 30
python3 -m zens_ink.search_performance --pages
python3 -m zens_ink.search_performance --page /pricing/ --start 2026-09-01
# Domain Rating (free Ahrefs public API, cached locally)
python3 -m zens_ink.domain_rating zens.ink competitor.com
python3 -m zens_ink.domain_rating --file domains.txt --csv dr.csv
Real DR output:
Domain Rating | 1 target(s) | Data: Domain Rating by Ahrefs (https://ahrefs.com/)
[1/1] zens.ink DR 21
Attribution note: DR output must keep the "Domain Rating by Ahrefs" credit line — it is a license requirement of the free API.
How to read the results
- GSC position 5-30 with impressions = quick-win zone: pages Google already likes. Improve title/on-page, add internal links, re-index.
- Position 30+ with impressions = crawling fine, ranking weak — content or authority problem, not technical.
- Impressions with zero clicks across the board = title/snippet problem.
- DR: compare against the sites actually ranking for your target keywords,
not industry averages. Results cache in
dr-cache.json;--no-cacheto refresh.
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.
- 2d ago First seen · 93 lines · 93 tokens per session scan A ac21fb4665b8
rank-tracking is a skill published in the GitHub repository ZensInk/zens-ink-seo-package (53 stars, last pushed 3d ago), licensed MIT. It adds 93 tokens to every session and 806 once invoked, about $0.0004 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-10-15.
Other skills, from other repositories
altorank
Run AltoRank through its hosted MCP server: readiness audits, Search Console, keyword research, and SEO drafts into a review queue.
content-creator
Self-configuring content creation pipeline with geo-lint validation. On first use, scans your project to learn its framework, content schema, categories, and authors, then creates SEO & GEO-optimized content matched to your brand voice. Validates every piece with geo-lint's 92 rules until zero violations. Triggers on…
geo-lint
SEO & GEO content linter — validates Markdown/MDX files for AI search visibility using 92 deterministic rules (35 GEO, 32 SEO, 14 content quality, 8 technical, 3 i18n). Runs an autonomous lint-fix loop: scan content, read structured violations, fix them, re-lint until clean. Use when optimizing content for AI…
geo-platform-optimizer
Platform-specific AI search optimization — audit and optimize for Google AI Overviews, ChatGPT, Perplexity, Gemini, and Bing Copilot individually.
vs-search-tuning-specify-policy-direction
Viking Search tuning for specified policy directions. Use this when the user provides specific queries, a type of query, or a business policy direction, and asks to boost, suppress, or fix a class of search results through request-parameter passthrough. You must only perform read-only baseline evaluation and…
vs-search-tuning-partial-case
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…