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/phillypmack/aura-agentWrote 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/mcp/phillypmack/aura-agent/aura)<a href="https://agentmods.dev/mcp/phillypmack/aura-agent/aura"><img src="https://agentmods.dev/badge/mcp/phillypmack/aura-agent/aura/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/mcp/phillypmack/aura-agent/aura"><img src="https://agentmods.dev/badge/mcp/phillypmack/aura-agent/aura.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
aura 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
{
"aura": {
"url": "https://aura.rohnelt.dev/mcp",
"type": "streamable-http"
}
}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 · 6 lines scan A 8ccc76f5679d
aura is an MCP server published in the GitHub repository phillypmack/aura-agent (0 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
acmi-mcp
Persistent agent memory via ACMI — Profile/Signals/Timeline. 16 tools on Upstash Redis. Runs locally from the @madezmedia/acmi-mcp npm package. Needs 2 environment variables to run.
synap
Persistent memory for AI agents — log and recall conversation context over MCP. Remote server at synap-mcp.maximem.ai.
quesen
Deterministic risk-decision engine and Agent Settlement Protocol for autonomous agents. Remote server at web-production-30ab5.up.railway.app.
gateway
Durable self for AI agents: one-call resume, memory, real browser, free chat + hire real humans. Remote server at agent.wingmanprotocol.com.
pensyve
Universal memory runtime for AI agents — episodic, semantic, and procedural memory. Remote server at mcp.pensyve.com.
portable-agent-memory
MCP server "portable-agent-memory" as configured in skywaller0/Portable-Agent-Memory. Runs locally from the portable-agent-memory Python package.