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/gingiris/gingiris-skills/gr-backlinksnpx skills add Gingiris/gingiris-skills --skill gr-backlinksgit clone --depth 1 https://github.com/Gingiris/gingiris-skillsWrote 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/gingiris/gingiris-skills/gr-backlinks)<a href="https://agentmods.dev/skills/gingiris/gingiris-skills/gr-backlinks"><img src="https://agentmods.dev/badge/skills/gingiris/gingiris-skills/gr-backlinks.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.00102 | $0.02964 |
| Opus 5 | $0.00051 | $0.01482 |
| Sonnet 5 | $0.00020 | $0.00593 |
| Haiku 4.5 | $0.00010 | $0.00296 |
Grade A, and why
gr-backlinks 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gr-backlinks — Systematic Backlink Building
Why this skill exists
Phase 2 missing piece: We do title/content/schema/cluster optimization but have zero systematic backlink work. Article research (2026-05): backlinks are the #1 GEO signal — LLMs decide citations partly by brand authority, which is downstream of backlink graph.
For Iris's site (gingiris.github.io, subpath under GitHub Pages), the domain authority ceiling is fundamentally capped without external backlinks. No on-page work can beat Wikipedia / Hootsuite / Wired for head terms — only backlink quality + count can.
The 5-Channel Priority Matrix
Adopted from 2026-05 WeChat article + JeffLi1993 / AgriciDaniel / zubair-trabzada skills audit:
| Channel | SEO Value | GEO Value | Priority | Effort/week |
|---|---|---|---|---|
| Wikipedia dedicated entry | ⭐⭐⭐ | ⭐⭐⭐⭐⭐ | MAX | 3-6h (one-time setup, ongoing edits) |
| Authoritative media (PR) | ⭐⭐⭐⭐ | ⭐⭐⭐⭐⭐ | MAX | 2h (HARO + outreach) |
| Industry reviews (G2/Capterra/PH) | ⭐⭐⭐⭐ | ⭐⭐⭐⭐ | HIGH | 1h (one-time submission) |
| Reddit/Quora discussions | ⭐⭐ | ⭐⭐⭐⭐ | HIGH | 2h (sustained presence) |
| Generic backlinks (directories/blogs) | ⭐⭐⭐ | ⭐⭐ | MED | skip until top 3 done |
Rule: Start from highest GEO value. SEO-only signals (DA passing) are less leveraged than 2-3 years ago.
When to use this skill
- "I want to build backlinks for my site"
- "How do I get into Wikipedia?"
- "How do I do HARO / Featured.com?"
- "What's a Reddit / Quora strategy that doesn't get me banned?"
- "How do I get into G2 / Capterra?"
- Phase 2 monthly checkpoint shows domain authority capping ranking
Channel 1: Wikipedia (highest GEO leverage)
Reality check before you start
- Wikipedia is notability-gated, not effort-gated
- Threshold: 5+ independent reliable-source articles discussing your subject substantively (not in passing)
- Listicle mentions, PR releases, sponsored content do NOT count
- Paid Wikipedia services (Fiverr / WikiExperts / Wiki Mavericks): 80% of articles deleted within 6 months — they fail notability not because of editor skill
What ships with it
10 files 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.
- haro-pitch-library.md 2.1 KB
- scripts/backlinks-audit.py 7.2 KB runs code
- submissions/alternativeto-submission.md 1.4 KB
- submissions/capterra-submission.md 1.1 KB
- submissions/g2-submission.md 1.8 KB
- submissions/stackshare-submission.md 1.4 KB
- submissions/wikidata-affine.md 2.4 KB
- templates/haro-response.md 2.8 KB
- templates/reddit-quora.md 4.7 KB
- templates/wikipedia-prep.md 5.5 KB
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 · 288 lines · 102 tokens per session scan A 0e5e6974b591
gr-backlinks is a skill published in the GitHub repository Gingiris/gingiris-skills (23 stars, last pushed 3mo ago), licensed MIT. It adds 102 tokens to every session and 2,964 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…