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.
git clone --depth 1 https://github.com/robzilla1738/roberts-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/robzilla1738/roberts-skills/scaffold)<a href="https://agentmods.dev/plugins/robzilla1738/roberts-skills/scaffold"><img src="https://agentmods.dev/badge/plugins/robzilla1738/roberts-skills/scaffold/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/plugins/robzilla1738/roberts-skills/scaffold"><img src="https://agentmods.dev/badge/plugins/robzilla1738/roberts-skills/scaffold.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
scaffold 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "scaffold",
"displayName": "Scaffold",
"version": "1.1.0",
"description": "Product-driven greenfield Next.js: intake profiles, typed env, Vitest, tRPC, Neon/Drizzle, optional Clerk, Vercel, intake add-ons (AI SDK, Resend, Stripe, Sentry, PostHog).",
"author": {
"name": "Robert Courson",
"url": "https://robertcourson.com"
},
"homepage": "https://github.com/robzilla1738/roberts-skills/tree/main/plugins/scaffold",
"repository": "https://github.com/robzilla1738/roberts-skills",
"license": "MIT",
"keywords": ["nextjs", "trpc", "drizzle", "clerk", "vercel", "vitest", "scaffold"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 106 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 scan A bc20bf039243
scaffold is a plugin published in the GitHub repository robzilla1738/roberts-skills (4 stars, last pushed 4mo 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
search-harness
Domain knowledge and roadmap for building a search harness for coding agents: CLI + skills design notes, API docs, and strategy.
developer-productivity-skills
API design, CLI development, SDK creation, documentation generation, debugging, and Git workflows.
backend-api-skills
API development, messaging, and real-time communication.
backend-ai-skills
AI/ML data engineering and model serving.
api-design-expert
Designing REST and GraphQL APIs: resource modeling, versioning, pagination, errors, and contracts.
nodejs-backend-expert
Node.js backend services with Express/Fastify/Hono: routing, middleware, auth, and async patterns.