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/MichaelCereda/stampoWrote 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/michaelcereda/stampo/plugin)<a href="https://agentmods.dev/plugins/michaelcereda/stampo/plugin"><img src="https://agentmods.dev/badge/plugins/michaelcereda/stampo/plugin/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/michaelcereda/stampo/plugin"><img src="https://agentmods.dev/badge/plugins/michaelcereda/stampo/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
stampo 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": "stampo",
"version": "1.0.0",
"description": "Create CLI tools from scratch or convert MCP tools into shell commands using stampo",
"author": {
"name": "Michael Cereda",
"url": "https://github.com/MichaelCereda"
},
"homepage": "https://github.com/MichaelCereda/stampo",
"repository": "https://github.com/MichaelCereda/stampo",
"license": "MIT",
"keywords": ["cli", "stampo", "mcp", "yaml", "shell"],
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 32 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 15 lines scan A 1ab67eff18e2
stampo is a plugin published in the GitHub repository MichaelCereda/stampo (5 stars, last pushed 1mo 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
cli-printing-press marketplace
Plugin marketplace listing 1 plugin: cli-printing-press.
cli-printing-press
Generate production Go CLIs from API descriptions or OpenAPI specs.
speakeasy
SDK generation and OpenAPI tooling with Speakeasy CLI.
type-foundry
Casts a spec and a CLI from closed apps that have no API. Drop an APK, IPA, EXE, DMG or traffic capture; a three-pass research method with built-in blind-spot diagnosis turns it into a feature spec, a reconstructed OpenAPI document, and optionally a CLI.
agent-deck
Complete guide for managing AI coding agent sessions via agent-deck CLI - session lifecycle, MCP management, groups, profiles, and automation.
jk
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.