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.
/plugin marketplace add aneja5/forge-skillsnpx agentmods add plugins/aneja5/forge-skills/marketplacegit clone --depth 1 https://github.com/aneja5/forge-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/plugins/aneja5/forge-skills/marketplace)<a href="https://agentmods.dev/plugins/aneja5/forge-skills/marketplace"><img src="https://agentmods.dev/badge/plugins/aneja5/forge-skills/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
forge-skills marketplace 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.
What it actually says
{
"name": "forge-skills",
"owner": {
"name": "Sahil Aneja",
"email": "[email protected]"
},
"metadata": {
"description": "Agentic Engineering toolkit — structured workflows from idea to shipped code"
},
"plugins": [
{
"name": "forge-skills",
"source": {
"source": "github",
"repo": "aneja5/forge-skills"
},
"description": "Agentic Engineering toolkit — 42 skills, 13 agent personas, 36 slash commands. Full UI chain (brand → design-system → components → pages → dataviz → polish) plus motion-system reference. forge:meta uses generated_from hash snapshots so upstream edits cascade zero downstream writes. /sync + /forge-migrate + /feedback + bin/forge-check.sh. TDD-tested skills.",
"homepage": "https://github.com/aneja5/forge-skills",
"repository": "https://github.com/aneja5/forge-skills",
"license": "MIT",
"category": "productivity",
"keywords": ["agentic-engineering", "tdd", "code-review", "architecture", "planning"],
"tags": ["skills", "agents", "pipeline", "contracts"]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 4d ago First seen · 27 lines scan A a11b32b3bd43
forge-skills marketplace is a plugin published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
lottie-design
Free Lottie animation skill: search, fetch, embed in React / React Native / Flutter / Vanilla web.
sprint
Orchestrate staged milestones with native subagents on Claude Code or Oh My Pi, plus codex or mimo executors on Claude Code.
neatcontext marketplace
Save Claude Code work as reusable, domain-aware context.
neatcontext
Save Claude Code work as reusable, domain-aware context.
backend-architecture
Small, opinionated architecture guide for production backend services across languages and frameworks.
code-cleanup
Evidence-first cleanup of agent trajectory residue, dead islands, split-brain authority, stale dependencies, and unnecessary code across repositories.