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 agentmods add skills/morningstar202604/agentseed/verify-before-codenpx skills add Morningstar202604/AgentSeed --skill verify-before-codegit clone --depth 1 https://github.com/Morningstar202604/AgentSeedWrote 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/morningstar202604/agentseed/verify-before-code)<a href="https://agentmods.dev/skills/morningstar202604/agentseed/verify-before-code"><img src="https://agentmods.dev/badge/skills/morningstar202604/agentseed/verify-before-code.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 | $0.00073 | $0.01682 |
| Opus 5 | $0.00036 | $0.00841 |
| Sonnet 5 | $0.00015 | $0.00336 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade A, and why
verify-before-code 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 4d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
20 files 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.
- references/DEFAULT-NORMS.md 4.3 KB
- references/HALLUCINATION-PATTERNS.ja.md 5.6 KB
- references/HALLUCINATION-PATTERNS.md 7.2 KB
- references/HALLUCINATION-PATTERNS.zh.md 6.8 KB
- references/PROMPT-POOL.ja.md 10 KB
- references/PROMPT-POOL.md 9.5 KB
- references/PROMPT-POOL.zh.md 8.6 KB
- references/SDD-CONTRACT.ja.md 3.4 KB
- references/SDD-CONTRACT.md 2.9 KB
- references/SDD-CONTRACT.zh.md 2.8 KB
- references/VENDOR-SOLUTIONS.ja.md 4.8 KB
- references/VENDOR-SOLUTIONS.md 4.3 KB
- references/VENDOR-SOLUTIONS.zh.md 3.9 KB
- references/VERIFICATION-CHECKLIST.ja.md 3.5 KB
- references/VERIFICATION-CHECKLIST.md 3.0 KB
- references/VERIFICATION-CHECKLIST.zh.md 2.9 KB
- scripts/check.ps1 4.0 KB runs code
- scripts/check.sh 3.6 KB runs code
- SKILL.ja.md 7.0 KB
- SKILL.zh.md 6.2 KB
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.
- 4d ago First seen · 150 lines · 73 tokens per session scan A f410d200d32d
verify-before-code is a skill published in the GitHub repository Morningstar202604/AgentSeed (7 stars, last pushed 4d ago), with no licence file. It adds 73 tokens to every session and 1,682 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
cargo
Router for the Cargo CLI skill bundle — load first for anything Cargo, and whenever a task spans two Cargo domains. Explains what each skill owns, declarative workspace-as-code (cargo-cdk) vs the imperative CLI, the UUID and slug flow between skills, async polling of runs and batches, end-to-end use cases, and the…
cargo-orchestration
Make Cargo actually run something, or show what it would run — execute one connector action, run a multi-step workflow, trigger a batch across a whole segment or model, message an AI agent, build or edit a node graph, draw a workflow, tool or play as a diagram, and query the runtime tables (runs, batches, spans…
cargo-ai
Build and configure AI agents inside Cargo — create an agent, choose its model and temperature, write its prompt, attach knowledge for retrieval (RAG), connect MCP tool servers, manage memories, and deploy releases. Triggers: "create an agent", "make an agent that", "give the agent our docs", "attach this knowledge…
cargo-analytics
Get data out of Cargo and measure what ran — download a run output, export a segment or model to CSV or JSON, and pull run and batch success and error counts. Triggers: "download the results", "export this to CSV", "give me the file", "how many succeeded", "what is my error rate", "send me the enriched list", "get the…
cargo-billing
Understand what Cargo is costing — remaining credits, usage broken down by workflow, connector, or agent, subscription state, and invoice history. Triggers: "how many credits do I have left", "what did that cost", "why is my bill so high", "am I about to run out", "will this fit in our budget", "show me my invoices"…
cargo-cdk
Manage a whole Cargo workspace as code — declare connectors, models, plays, tools, agents, MCP servers, segments, context, folders, files, workers, and apps in TypeScript, then reconcile them with cargo-ai cdk (init → types → plan → deploy), the way you would run Pulumi or the AWS CDK. Triggers: "as code", "in git"…