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 abryfs/agent-stenpx agentmods add plugins/abryfs/agent-ste/marketplacegit clone --depth 1 https://github.com/abryfs/agent-steGrade A, and why
agent-ste 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
{
"$schema": "https://json.schemastore.org/claude-code-marketplace.json",
"name": "agent-ste",
"owner": {
"name": "Abraham Sheer Dela Vega",
"url": "https://github.com/abryfs"
},
"metadata": {
"description": "Marketplace for the agent-ste plugin: ASD-STE100 Simplified Technical English for agents.",
"version": "1.0.2"
},
"plugins": [
{
"name": "agent-ste",
"source": "./",
"description": "Write technical and agent-facing text in ASD-STE100 Simplified Technical English. Benchmarked: 95.5% fewer STE violations than baseline across 12 models.",
"category": "writing",
"tags": ["ste", "asd-ste100", "technical-writing", "documentation"]
}
]
}
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.
- 2d ago First seen · 22 lines scan A e136e9d0d801
agent-ste is a plugin published in the GitHub repository abryfs/agent-ste (4 stars, last pushed 21d 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
codspeed
CodSpeed plugin for Claude Code helping with performance measurement and optimization.
spmind
Plugin marketplace listing 1 plugin: spmind.
slopgent
Shape the agent's own replies so they are honest about what ran, action-first, and plain — without dropping load-bearing precision.
orders-pack
Bundles a slash command (report-orders) and a skill (processing-watch) that both reach the workspace's ordersdb MCP server.
skill-optimizer
Benchmark, evaluate, and optimize skills to ensure reliable performance across all LLMs.
modelharness
Fable 5 behavioral patterns as a harness for Opus 4.8: grounded progress, self-verification loops, delegation triggers, file-based memory, autonomy calibration. Zero-config: installs a SessionStart hook; skills auto-trigger.