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.
git clone --depth 1 https://github.com/skillselion/skillselion-mcpWrote 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/rules/skillselion/skillselion-mcp/wiki-ingest-push)<a href="https://agentmods.dev/rules/skillselion/skillselion-mcp/wiki-ingest-push"><img src="https://agentmods.dev/badge/rules/skillselion/skillselion-mcp/wiki-ingest-push/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/rules/skillselion/skillselion-mcp/wiki-ingest-push"><img src="https://agentmods.dev/badge/rules/skillselion/skillselion-mcp/wiki-ingest-push.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.00250 | $0.00250 |
| Opus 5.5 | $0.00100 | $0.00100 |
| Sonnet 5.5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
wiki-ingest-push 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 2mo 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
Wiki ingest + push
The knowledge layer is icidab/ellelion-wiki, not this repo. Durable knowledge (decision + rationale, market fact, learning, status change) must be ingested there and pushed. A Cloud VM is discarded; an unpushed wiki commit dies with it.
- Resolve the wiki checkout:
~/Desktop/root/wiki, siblingellelion-wiki, orgh repo clone icidab/ellelion-wiki "$HOME/wiki". - Update pages, bump
updated:, add onelog.mdline. Schema: that repo'sCLAUDE.md. - Commit in the wiki repo only, then
git push origin HEAD(orscripts/push-main.sh). Do not finish while the wiki isaheadof origin. - If nothing was durable, write that in the reply (
no ingest: …). Do not skip in silence.
Product-repo commits (this repo) still wait for an explicit ask. Wiki ingest does not. Never put secret values in the wiki.
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.
- 2mo ago First seen · 16 lines · 250 tokens per session scan A c101a9ecde89
wiki-ingest-push is a cursor rule published in the GitHub repository skillselion/skillselion-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 250 tokens to every session, about $0.0010 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-08-31.
Other cursor rules, from other repositories
dev_workflow
Guide for task-driven development workflows.
maidan-claimant
Take coding work from a Maidan queue as a session claimant (claim a task routed to sessions, do it here, run the pre-push gate, hand the change back so Maidan opens the draft pull request, report usage, start review, release). Use when asked to take, claim or work Maidan tasks, or to follow up on a Maidan pull request…
gsd-ship-labels
After /gsd-ship creates a PR, always run gsd-ship-post (labels + optional changeset).
conventional-commits
Enforce Conventional Commits format for all commit messages.
pr-automation
Cursor rule "pr-automation" from floriscornel/todo-mcp, covering pull request guidelines, pre-pr checklist, pr description template, summary and changes.
git-auto-commit
This rule ensures that after Cursor IDE automatically performs changes from Git commits, the modified files are automatically committed back to Git using the conventional commit format. This maintains a clear and consistent commit history that explains what changes were made and why.