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 catcatcatstudio/cat-skills --skill elevategit clone --depth 1 https://github.com/catcatcatstudio/cat-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/catcatcatstudio/cat-skills/elevate)<a href="https://agentmods.dev/skills/catcatcatstudio/cat-skills/elevate"><img src="https://agentmods.dev/badge/skills/catcatcatstudio/cat-skills/elevate.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.1 | $0.00081 | $0.01488 |
| Opus 5 | $0.00041 | $0.00744 |
| Sonnet 5 | $0.00016 | $0.00298 |
| Haiku 4.5 | $0.00008 | $0.00149 |
Grade A, and why
elevate 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 7d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/elevate — Expert Elevation Skill
Step 1: Adopt Domain Expert Mindset
Identify the domain from conversation context, open files, and project state. Adopt the mindset of a top-tier practitioner in that specific field — not generic "try harder" but the actual perspective of someone with 15+ years of deep expertise.
Examples:
- Landing page → senior product designer + conversion specialist
- Copy/content → experienced editor who's shipped bestsellers
- Project plan → seasoned technical lead who's built and scaled products
- Code → senior engineer at a top-tier company
- Brand → creative director at a respected agency
If the domain spans multiple fields, identify the primary one and note secondary lenses.
State the expert lens in one line before proceeding:
Thinking as: [specific expert role with domain context]
Step 2: Understand Purpose
Before proposing anything, identify WHY this work exists. Not the task — the goal behind the task.
- Who is the audience/end user?
- What experience or outcome is this trying to create?
- What does success look like?
If purpose is obvious from context, state it in one line and move on. If genuinely unclear, ask — but frame it as a quick clarifying question, not an interrogation.
Step 3: Assess Context & Decide Approach
Evaluate how much context is available. Follow exactly one path:
Path A — Rich context (task, files, conversation history are clear): Skip questions entirely. Go straight to Step 4.
Path B — Partial context (domain clear, focus ambiguous): Ask ONE targeted question. Use multiple choice when possible:
"I see [X], [Y], and [Z] in play. Which should I focus on? Or all of them?"
Then proceed to Step 4.
Path C — Bare invocation (almost nothing to work with): Examine recent conversation, open files, project state. State what you found. Ask what to elevate with suggested options based on what you see. Wait for response before proceeding.
The rule: Only ask if the answer would meaningfully change the output. If you can confidently identify the target and purpose, just go.
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.
- 7d ago First seen · 121 lines · 81 tokens per session scan A ef6f27c5fdee
elevate is a skill published in the GitHub repository catcatcatstudio/cat-skills (3 stars, last pushed 11d ago), licensed MIT. It adds 81 tokens to every session and 1,488 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
watch
Watch live IDX turnover and order books for unusual activity — value surges, auto-reject approach, one-sided depth, walls appearing or withdrawn, quiet stocks waking up, UMA flags — plus delayed print-by-print attribution and end-of-day broker context. Use when the user runs /watch, or asks what is trading right now…
stockbit-status
Check whether the Stockbit session is still valid — main session expiry, whether trading credentials are stored, and the current trading mode. Use when the user asks "am I still logged in to Stockbit", "has my session expired", "is trading on", or when a stockbit MCP tool starts failing with an auth error.
stockbit-auth
Log in to Stockbit and capture the session for this server — opens the browser login flow and verifies the token was stored. Use when the user asks to log in or re-authenticate to Stockbit, or after a status check reports the session expired, HTTP 401, or logged out.
recursive-decomposition
Handle tasks that exceed the context window by decomposing them: size and filter the input, chunk it, run recursive sub-agents on independent parts, verify on small windows, and synthesise programmatically, following the Recursive Language Models (RLM) research by Zhang, Kraska and Khattab (2025). Use when a task…
bandar-check
Answer "who is accumulating this stock?" for an IDX ticker using Stockbit broker-flow data. Use when the user asks about bandar, big money, accumulation, distribution, foreign flow, asing, or who is on the other side of the tape.
trade-with-guardrails
Place an order through the user's own Stockbit account safely — check the mode, size the position from a risk budget, preview, read the summary back to the human, and only then write. Use when the user asks to buy, sell, amend or cancel an order, or to size a trade.