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/ApeWorX/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/apeworx/skills/ape)<a href="https://agentmods.dev/plugins/apeworx/skills/ape"><img src="https://agentmods.dev/badge/plugins/apeworx/skills/ape/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/apeworx/skills/ape"><img src="https://agentmods.dev/badge/plugins/apeworx/skills/ape.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ape 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
{
"name": "ape",
"description": "Skills for extending Ape Framework with custom plugins and designing smart contract protocols",
"source": "./",
"strict": false,
"skills": [
"./ape/protocol-design",
"./ape/writing-plugins"
]
}What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 146 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#ape 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.
- 1mo ago First seen · 10 lines scan A 6d5ebf881b67
ape is a plugin published in the GitHub repository ApeWorX/skills (5 stars, last pushed 8mo 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-09-03.
Other plugins, from other repositories
python-package
Research-backed best practices for building modern, production-grade Python packages — project structure, pyproject.toml, typing, testing, CI/CD, documentation, versioning, API design, packaging, security, and developer experience.
pykx-knowledge
KDB-X Python (pykx) workflows — using kdb+/q from Python, conversions between Python and q types, and KDB-X Python API guidance.
ida-plugin-development
Skills, knowledge, and scripts for developing plugins for IDA Pro in Python, using idiomatic patterns, lessons, and tricks.
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
oat-publish-python
Python release management: cleanup, version bump, uv build, GitHub release, publish monitoring.
modern-python
Modern Python best practices. Use when creating new Python projects, and writing Python scripts, or migrating existing projects from legacy tools.