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 Belkins/revenue-osnpx agentmods add plugins/belkins/revenue-os/plugingit clone --depth 1 https://github.com/Belkins/revenue-osGrade A, and why
revenue-os 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "revenue-os",
"displayName": "Revenue OS",
"version": "1.0.6",
"description": "A practical monetization toolkit for moving from code to customers to revenue.",
"author": {
"name": "Vladyslav Podoliako",
"url": "https://vladyslavpodoliako.com/"
},
"repository": "https://github.com/Belkins/revenue-os",
"homepage": "https://github.com/Belkins/revenue-os#readme",
"license": "MIT",
"keywords": [
"monetization",
"sales",
"marketing",
"revenue",
"ideal-customer-profile",
"value-proposition",
"pricing",
"outreach",
"customer-acquisition"
],
"commands": [
"./commands/ros.md",
"./commands/ros-audit.md",
"./commands/ros-competitors.md",
"./commands/ros-first-dollar.md",
"./commands/ros-icp.md",
"./commands/ros-landing-page.md",
"./commands/ros-objections.md",
"./commands/ros-outreach.md",
"./commands/ros-pricing.md",
"./commands/ros-value-prop.md"
]
}
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 · 38 lines scan A 77550da16065
revenue-os is a plugin published in the GitHub repository Belkins/revenue-os (29 stars, last pushed 27d 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-30.
Other plugins, from other repositories
markifact
Run Google Ads, Meta Ads, GA4, Shopify, and 20+ more platforms from Claude. 1000+ operations with human-in-the-loop on every write.
alibabacloud-agent-toolkit
Plugin marketplace listing 3 plugins: alibabacloud-core, alibabacloud-spec-ops, alibabacloud-ecs-ops.
neatcontext
Save Claude Code work as reusable, domain-aware context.
talk-to-anyone
Turn any public figure into your personal coach, living or historical. /coach researches the person across the web, pulls real transcripts when they have video anywhere on YouTube, builds a persona, and talks to you as them until you switch or end.
arcgram
Plugin marketplace listing 1 plugin: arcgram.
romek-plugins
Claude Code plugins by Roman Rozenberger.