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/dotlas/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/dotlas/skills/community-coding)<a href="https://agentmods.dev/plugins/dotlas/skills/community-coding"><img src="https://agentmods.dev/badge/plugins/dotlas/skills/community-coding.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
community-coding 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 3d 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": "community-coding",
"description": "Code quality, review, and deployment skills vendored from the web.",
"source": "./",
"strict": false,
"skills": [
"./skills/community/coding/improve-codebase-architecture",
"./skills/community/coding/qa",
"./skills/community/coding/resolving-merge-conflicts",
"./skills/community/coding/vercel-optimize",
"./skills/community/coding/vercel-react-best-practices"
]
}What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 296 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#community-coding 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.
- 3d ago First seen · 13 lines scan A 6aea39e02f56
community-coding is a plugin published in the GitHub repository dotlas/skills (2 stars, last pushed 10d 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-09-03.
Other plugins, from other repositories
fix-pr
Fix PR review comments automatically with context-aware patches.
pr-prepare
Prepare a structured PR description that discloses AI authorship, classifies change impact, and runs the pre-submit checklist.
code-review-assistant
Automated code review with severity levels and actionable feedback.
ci-review
CI-optimized code review: multi-agent parallel review with confidence scoring and atomic GitHub PR review posting via gh api.
workflow
Code review and worktree workflow commands.
gh-dash
GitHub PR dashboard with CI/CD status indicators and merge capability.