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/Ramsbaby/jarvisWrote 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/ramsbaby/jarvis/jarvis-plan-review)<a href="https://agentmods.dev/plugins/ramsbaby/jarvis/jarvis-plan-review"><img src="https://agentmods.dev/badge/plugins/ramsbaby/jarvis/jarvis-plan-review.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
jarvis-plan-review 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 8d 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": "jarvis-plan-review",
"version": "0.1.0",
"description": "11-section rigorous design plan review (problem, scope, architecture, security, observability, deployment, performance, reliability, testing, maintainability, migration). Adapted from gstack /plan-ceo-review for sole-developer + AI-pair-programming workflows.",
"author": {
"name": "Ramsbaby",
"url": "https://github.com/Ramsbaby/jarvis"
},
"homepage": "https://github.com/Ramsbaby/jarvis/tree/main/plugins/jarvis-plan-review",
"license": "MIT",
"keywords": ["design-review", "plan-review", "architecture", "11-section"]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 74 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.
- 8d ago First seen · 13 lines scan A 43bb6704964b
jarvis-plan-review is a plugin published in the GitHub repository Ramsbaby/jarvis (16 stars, last pushed 16d 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
cognition
Live control of one Discord server used as a lab for bots and programming experiments. Read the server, build systems as Registry data, run test sessions, schedule work, and gate anything irreversible behind a written preview.
marketing-team
Marketing team — 3 agents: Ink, Buzz, Pitch.
jk
GitHub CLI-style interface for Jenkins controllers - create multibranch jobs, inspect config.xml, and manage runs, logs, artifacts, credentials, nodes, and queues.
looptimal
Turns an objective into a delivered, VERIFIED OUTCOME: frames a hash-pinned sealed acceptance suite, designs the right loop (the loop-design wizard, formerly LoopPrint), war-games it forward, executes with dynamic domain-expert sub-agents (maker != checker), and gates completion on a separate verifier re-running the…
claude-superskills marketplace
Plugin marketplace listing 1 plugin: claude-superskills.
lv
Compatibility namespace for the Elixir/Phoenix plugin's /lv: commands.