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 Ce-Legend/ce-legend-skills --skill submit-backlinksgit clone --depth 1 https://github.com/Ce-Legend/ce-legend-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/ce-legend/ce-legend-skills/submit-backlinks)<a href="https://agentmods.dev/skills/ce-legend/ce-legend-skills/submit-backlinks"><img src="https://agentmods.dev/badge/skills/ce-legend/ce-legend-skills/submit-backlinks/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/ce-legend/ce-legend-skills/submit-backlinks"><img src="https://agentmods.dev/badge/skills/ce-legend/ce-legend-skills/submit-backlinks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 90 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 102 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00055 | $0.02815 |
| Opus 5 | $0.00028 | $0.01407 |
| Sonnet 5 | $0.00011 | $0.00563 |
| Haiku 4.5 | $0.00006 | $0.00281 |
Grade A, and why
submit-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 yesterday.
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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submit Backlinks
Goal
Turn a target-site brief and a raw backlink pool into a qualified queue, execute only authorized actions, verify explicit evidence, and keep submission actions separate from public backlinks.
Treat this skill as a baseline workflow. Follow the user's explicit goals, constraints, tools, and authorization choices over its defaults. Adapt source selection, thresholds, batch size, order, and output format when useful; preserve evidence integrity, privacy, and explicit boundaries for payment, identity verification, and site changes.
Guide the first run
Read references/guided-onboarding.md when the user provides only a site URL, gives an incomplete request, or asks how to begin.
Use these safe defaults when the user does not specify them:
- qualify each candidate before execution; show a queue first when the user requests planning or approval;
- target up to 10 qualified opportunities in the first queue;
- use free routes only;
- allow reciprocal candidates into the queue but require approval before changing the site;
- use
queue_onlyfor research requests; a request to submit startsauthorized_continuouswithin the stated scope; - after authorization, use
authorized_continuousand continue through qualified free platforms without repeated confirmation; - prefer whichever supported SEO tool is currently open and authenticated instead of requiring a named provider;
- for competitor-backlink discovery, find 10–20 relevant competitors when available and build a broad raw pool before ranking or qualification;
- remember the provider only after a successful read or export, without storing account or session data;
- use local JSONL or stdout unless a tracker is configured;
- infer public product facts from the live site before asking questions.
Recover prior campaign results and existing authorization before starting a continuation. Do not restart onboarding or ask the user to authorize an action already covered by the conversation. Keep missing personal facts separate from missing permission.
What ships with it
23 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.
- agents/openai.yaml 312 B
- assets/campaign-brief.example.json 1.2 KB
- assets/candidate-pool.example.csv 288 B
- assets/lark-config.example.json 648 B
- references/browser-execution.md 6.1 KB
- references/candidate-pool.md 4.1 KB
- references/discovery-sources.md 4.1 KB
- references/guided-onboarding.md 3.6 KB
- references/high-volume-outreach.md 3.8 KB
- references/oauth-session.md 2.4 KB
- references/platform-playbook.md 3.0 KB
- references/preferences.md 1.9 KB
- references/reciprocal-links.md 2.5 KB
- references/tracker.md 2.4 KB
- scripts/init_campaign.py 3.0 KB runs code
- scripts/preferences.py 5.0 KB runs code
- scripts/prepare_pool.py 9.0 KB runs code
- scripts/record_backlink.py 13 KB runs code
- tests/test_init_campaign.py 2.6 KB runs code
- tests/test_preferences.py 1.7 KB runs code
- tests/test_prepare_pool.py 2.3 KB runs code
- tests/test_record_backlink.py 2.8 KB runs code
- tests/test_skill_package.py 2.9 KB runs code
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.
- yesterday Changed · +18 lines 89c6fbdad1b6
- 10d ago First seen · 198 lines · 55 tokens per session scan A 0bae58c3f926
submit-backlinks is a skill published in the GitHub repository Ce-Legend/ce-legend-skills (54 stars, last pushed 2d ago), licensed MIT. It adds 55 tokens to every session and 2,815 once invoked, about $0.0003 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.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
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…