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/frane/agentedWrote 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/frane/agented/plugin)<a href="https://agentmods.dev/plugins/frane/agented/plugin"><img src="https://agentmods.dev/badge/plugins/frane/agented/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/frane/agented/plugin"><img src="https://agentmods.dev/badge/plugins/frane/agented/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agented 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 28d 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": "agented",
"description": "A text editor for LLMs, not humans.",
"version": "0.7.2",
"author": {
"name": "Frane Bandov",
"url": "https://github.com/frane"
},
"homepage": "https://github.com/frane/agented",
"repository": "https://github.com/frane/agented",
"license": "Apache-2.0",
"keywords": ["editor", "stateful", "undo-tree", "lsp", "mcp"]
}
What it installs
The manifest is a name and a version. 1 skill, 1 MCP server travel with it, and installing the plugin installs all of them — 14 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.
- 28d ago Changed c966a56ce026
- 1mo ago First seen · 14 lines scan A 465e6ad4c1a9
agented is a plugin published in the GitHub repository frane/agented (5 stars, last pushed 24d 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-08-31.
Other plugins, from other repositories
sabx
SABnzbd CLI - control downloads, queues, RSS feeds, and automation via terminal.
agent-deck
Complete guide for managing AI coding agent sessions via agent-deck CLI - session lifecycle, MCP management, groups, profiles, and automation.
better-fullstack
Let your AI assistant scaffold and extend Better Fullstack projects through the official MCP server and focused skills.
bkt
Bitbucket CLI - manage repos, PRs, branches, issues, webhooks, and pipelines for both Data Center and Cloud.
claude-status-bar
Menu bar status indicator for Claude Code: animated spark, elapsed timer, and open/close lifecycle.
pad
Talk to your project. Pad is local-first project management for developers and AI agents — this plugin gives Claude Code a conversational Pad skill, typed shortcuts (/pad:status, /pad:capture, /pad:onboard, /pad:connect, /pad:disconnect), a /pad-pane side panel for browsing and updating your workspace, and…