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 mdsakalu/agent-pluginsnpx agentmods add plugins/mdsakalu/agent-plugins/marketplacegit clone --depth 1 https://github.com/mdsakalu/agent-pluginsGrade A, and why
agent-plugins 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 2d 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": "agent-plugins",
"owner": {
"name": "Michael Sakaluk"
},
"plugins": [
{
"name": "reflecting-on-skills",
"description": "Analyze skill usage after each invocation and suggest improvements via PostToolUse hook-driven self-reflection.",
"source": "./reflecting-on-skills"
},
{
"name": "suggesting-skills",
"description": "Analyze Claude Code sessions to identify repeated patterns and suggest new skills based on usage.",
"source": "./suggesting-skills"
},
{
"name": "writing-skills",
"description": "Guide for authoring well-structured Agent Skills \u2014 SKILL.md structure, naming conventions, and best practices.",
"source": "./writing-skills"
},
{
"name": "workspace",
"description": "Universal workspace management \u2014 JJ workspaces, notes, PR/Jira auto-capture, cross-repo navigation.",
"source": "./workspace"
}
]
}
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.
- 2d ago First seen · 29 lines scan A 6b10bb789a74
agent-plugins is a plugin published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 2mo 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
agent-teams
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams.
agency-os
Run your work like an AI agency, from a single Notion board. Agents discuss, plan, and execute tasks in parallel with dependency ordering and model routing.
oh-my-agent
Plugin marketplace listing 1 plugin: oma.
anti-slop
The antislop skill/plugin. Anti Slop: Rules for AI Coding Agents.
supergoal
Supergoal marketplace — deep planning + autonomous /goal-driven execution for Claude Code and Codex.
supergoal
Plan and autonomously build a software task end-to-end. Recons the codebase, applies preloaded memory, decomposes into the right number of phases, gets one confirmation, then prepares a single ready-to-paste /goal command — one paste between you and done — that drives execution to completion with built-in retry…