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 markskrypka/stemnpx agentmods add plugins/markskrypka/stem/marketplacegit clone --depth 1 https://github.com/markskrypka/stemGrade A, and why
stem 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 yesterday.
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": "stem",
"metadata": {
"description": "Engineering discipline for coding agents: size the work, keep every change on the record, verify against intent, never lose a session."
},
"owner": {
"name": "Mark Skrypka"
},
"plugins": [
{
"name": "stem",
"description": "One skill carrying the whole discipline, two agents, per-host session protection. Plan first, build clean, keep every change on the record. stem.cooking",
"version": "0.1.0",
"author": {
"name": "Mark Skrypka"
},
"source": "./",
"category": "development",
"homepage": "https://stem.cooking",
"repository": "https://github.com/markskrypka/stem",
"tags": ["engineering", "discipline", "workflow", "planning", "worklog", "skills", "agents"]
}
]
}
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.
- yesterday First seen · 25 lines scan A 0f5b8f5c109d
stem is a plugin published in the GitHub repository markskrypka/stem (2 stars, last pushed 27d ago), licensed Apache-2.0. 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
humanizer
Install Humanizer as a Claude plugin.
ainb-hooks
Emit every safely observable Claude Code lifecycle event into Hangar's durable provider log. User-facing events still reach ainb-notifyd over its Unix socket. The same notify.sh powers ATC structured control when installed with AINBMANAGED=atc. stallguard.py additionally blocks turn-end when a session would idle on i.
draft-plugins
Plugin marketplace listing 1 plugin: draft.
google-search-console-mcp
Plugin marketplace listing 1 plugin: google-search-console-mcp.
tdmcp
Plugin marketplace listing 1 plugin: tdmcp.
uizze
Connect Claude Code to UIZZE's focused UI references and hosted materials.