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 itsbroken-ai/forge-plugin --skill seedgit clone --depth 1 https://github.com/itsbroken-ai/forge-pluginWrote 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/itsbroken-ai/forge-plugin/seed)<a href="https://agentmods.dev/skills/itsbroken-ai/forge-plugin/seed"><img src="https://agentmods.dev/badge/skills/itsbroken-ai/forge-plugin/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/skills/itsbroken-ai/forge-plugin/seed"><img src="https://agentmods.dev/badge/skills/itsbroken-ai/forge-plugin/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.00106 | $0.02799 |
| Opus 5.5 | $0.00042 | $0.01120 |
| Sonnet 5.5 | $0.00021 | $0.00560 |
| Haiku 4.5 | $0.00011 | $0.00280 |
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 1mo 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
forge:seed — Safe Ethical Experimentation and Development
You want to try something. Good. That instinct is how good software gets built.
This skill exists to make sure your experiments teach you something instead of waking you up at 3am. The philosophy is simple: push boundaries, but know where the walls are before you start swinging.
SEED is not a gate. It is a guide. The answer is almost never "don't do that." The answer is "do that, and here's how to keep it from catching fire."
The SEED Principles
Safe
Every experiment should have a blast radius you can contain. If the worst case is "I restart my dev server," go wild. If the worst case is "production database gets wiped," you need a sandbox first.
Containment is not about fear. It is about knowing what breaks and how far the break travels. A controlled explosion is science. An uncontrolled explosion is a resume-generating event.
Ask yourself: "If this goes completely sideways, what is the worst thing that happens?" If you can live with the answer, proceed. If you cannot, shrink the blast radius until you can.
Ethical
Every system you build will eventually be used by someone who is not you, in a way you did not expect. That is not paranoia, it is software development.
"Could this be misused?" is always a valid question. Not because you need to prevent every possible abuse before writing line one, but because thinking about it early costs nothing and thinking about it after an incident costs everything.
This is not about being heavy-handed. It is about being thoughtful. Consider the humans downstream of your code: the users, the data subjects, the ops team who will be paged when something breaks.
Experimentation
Push boundaries. Try things. Break things in controlled environments. The goal is learning, not perfection.
The developer who never experiments ships stale code. The developer who experiments without guardrails ships broken code. You want to be the developer who experiments with intention: clear hypothesis, contained environment, observable results.
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.
- 1mo ago First seen · 217 lines · 106 tokens per session scan A 8632e85c89c0
seed is a skill published in the GitHub repository itsbroken-ai/forge-plugin (11 stars, last pushed 6d ago), licensed MIT. It adds 106 tokens to every session and 2,799 once invoked, about $0.0004 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-30.
Other skills, from other repositories
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.