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 AdvayRoy/slate-skills --skill slate-rungit clone --depth 1 https://github.com/AdvayRoy/slate-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/advayroy/slate-skills/slate-run)<a href="https://agentmods.dev/skills/advayroy/slate-skills/slate-run"><img src="https://agentmods.dev/badge/skills/advayroy/slate-skills/slate-run/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/advayroy/slate-skills/slate-run"><img src="https://agentmods.dev/badge/skills/advayroy/slate-skills/slate-run.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.00034 | $0.00381 |
| Opus 5 | $0.00017 | $0.00191 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
slate-run 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 10d 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
slate-run
Fast execution loop for real projects.
Mission
Maximize useful progress per token during active repo work.
Use for Project X, AG Trade, repo maintenance, bugfix loops, dashboard edits, risk-control changes, and any task where the agent should avoid broad scanning or long narration.
Loop
- Restate goal in one line.
- Inspect only relevant files first.
- Make one focused change.
- Run smallest relevant check first.
- Run broader check only when needed.
- Report compact proof.
- Suggest next prompt/command.
Output
Goal:
Files:
Action:
Check:
Result:
Next:
Efficiency rules
- No full repo scan unless task requires it.
- No architecture essay before patch.
- No repeated context user already provided.
- No long logs; quote shortest decisive line.
- No multi-feature patch unless user asks.
- Prefer targeted tests before full suites.
- If blocked, state blocker + exact next action.
Safety boundary
For trading, payments, auth, secrets, deploys, destructive DB ops, or real capital:
- Stop before live execution.
- State boundary clearly.
- Offer dry-run, simulation, manual approval gate, or test harness.
- Do not add wallet keys, private keys, real order placement, or automatic capital deployment.
Example
Goal: add rejected-trade journal tile.
Files: dashboard.py, btc5m_journal.py.
Action: added rejected_count + reason summary.
Check: `python cli.py verify` passed.
Result: dashboard shows fills + rejects.
Next: add reject-rate trend chart.
What ships with it
1 file 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.
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.
- 10d ago First seen · 69 lines · 34 tokens per session scan A f9b907813036
slate-run is a skill published in the GitHub repository AdvayRoy/slate-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 381 once invoked, about $0.0002 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.