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/j-256/agent-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/j-256/agent-skills/dsc)<a href="https://agentmods.dev/plugins/j-256/agent-skills/dsc"><img src="https://agentmods.dev/badge/plugins/j-256/agent-skills/dsc/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/j-256/agent-skills/dsc"><img src="https://agentmods.dev/badge/plugins/j-256/agent-skills/dsc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
dsc 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "dsc",
"version": "0.1.0",
"description": "Salesforce developer documentation skills for API reference scraping, endpoint help, and multi-call scenarios.",
"author": {
"name": "James Klein"
},
"license": "MIT",
"keywords": [
"salesforce",
"developer-salesforce-com",
"scapi",
"ocapi",
"api-reference"
]
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 218 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.
- 1mo ago First seen · 18 lines scan A 6e04b18fbe99
dsc is a plugin published in the GitHub repository j-256/agent-skills (2 stars, last pushed yesterday), 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
aws-agent-skills
Collection of AWS engineering skills for IAM, Lambda, DynamoDB, S3, and 14 other core AWS services.
fuse-php
Expert modern PHP 8.5/8.4 for non-Laravel projects — libraries, standalone Symfony components, Slim, API-first apps, and CLI tools, with PER Coding Style 3.1, PHPStan, and SOLID principles.
fuse-nextjs
Expert Next.js 16 + React 19 with App Router, Server Components, Prisma 7, and Better Auth.
rails-consultant
A collection of skills for Rails development and consulting, with an emphasis on learning, communication, and client success.
docs
Documentation that stays true to the code: architecture decision records with an /adr command, READMEs verified against the repository, developer guides in the four documentation types, and OpenAPI specifications kept in sync in CI.
system-design-skills
A divide-and-conquer wiki of system-design skills. Reason about a design problem one part at a time -- requirements, capacity, APIs, storage, caching, load balancing, messaging, consistency, resilience, delivery, and scaling -- each with generic recipes, cloud-provider variants (AWS/Azure/GCP/Temporal), explicit trade.