Borrowing it
Nothing to install: this file belongs to stevenn/ctxlayer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stevenn/ctxlayer/main/.claude/commands/seed.mdgit clone --depth 1 https://github.com/stevenn/ctxlayerWrote 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/commands/stevenn/ctxlayer/seed)<a href="https://agentmods.dev/commands/stevenn/ctxlayer/seed"><img src="https://agentmods.dev/badge/commands/stevenn/ctxlayer/seed/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/commands/stevenn/ctxlayer/seed"><img src="https://agentmods.dev/badge/commands/stevenn/ctxlayer/seed.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.00012 | $0.00169 |
| Opus 5.5 | $0.00005 | $0.00068 |
| Sonnet 5.5 | $0.00002 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
seed 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
Run bun run seed:local. The seed script inserts three teams (Platform, Web,
Data) and two products (Checkout, Search) so the org-IA surfaces — team/product
pickers, visibility grants, doc tags — have something to render. Ids are
deterministic and every insert is INSERT OR IGNORE, so it is idempotent.
It does NOT seed upstreams or docs. Docs need a real created_by user, and
inserting a fake user row would bypass the IdP allowlist; register an upstream
through /app/admin/upstreams and create docs by signing in.
seed:remote is a separate command and must be explicit — see
scripts/seed.mjs.
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 · 12 tokens per session scan A 5beeaac8fc3b
seed is a command published in the GitHub repository stevenn/ctxlayer (12 stars, last pushed 17d ago), licensed MIT. It adds 12 tokens to every session and 169 once invoked, about $0.0000 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 commands, from other repositories
hyperliquid-risk
Mission-critical real-time risk monitoring system with automated alerts, circuit breakers, and emergency shutdown for live Hyperliquid trading by ae.ltd.
worktree-clean
Clean up finished git worktrees by removing directories and pruning references.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.