Agentaegis Mcp— agent skill

Agentaegis Mcp — independently scanned and version-tracked by SaferSkills.

by astafford8488·Agent Skill·github.com/astafford8488/agentaegis-mcp

Is Agentaegis Mcp safe to install?

SaferSkills independently audited Agentaegis Mcp (Agent Skill) and scored it 87/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 3 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

Score
87/100
●●●●●●●●●
↑ +0 since first scan (87 → 87)Re-scan~30s
Latest scan
ScannedJun 24, 2026 · 33d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings3 warnings · 0 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
64
22.4 pts
Supply chainhash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenancestaleness, pinning, CI
15%
100
15.0 pts
TransparencySKILL.md, perms, README
15%
100
15.0 pts
Communityinstalls, verify, response
15%
100
15.0 pts

Findings & checks · 3 flagged

Securityscore 64 · 3 findings
MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · launch/reddit/04-r-cybersecurity.md×2
MEDIUMit fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.
Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted
excerptlaunch/reddit/04-r-cybersecurity.md· markdown
111 
112## Anti-patterns specific to this sub
113 
114- DO NOT mention "AI" or "agent" or "LLM" in the title or first paragraph. The sub will not
… (7 chars elided on L114)
115- DO NOT mention "USDC" / "crypto" / "x402" / "blockchain" in the post body. Mentioning cryp
… (108 chars elided on L115)
116- DO show real code, real findings, real numbers. r/cybersecurity respects evidence
Occurrences
2 occurrences · first at L113, also L115
Show all 2 locations
Line
File
L113
launch/reddit/04-r-cybersecurity.md
L115
launch/reddit/04-r-cybersecurity.md
How to fix
Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.
  1. Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
  2. Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-IMPERATIVE-01sha2562e4da82cc593cffcrubric 365aacaView on GitHub
MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · launch/reddit/05-r-ethereum.md
MEDIUMit fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.
Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted
excerptlaunch/reddit/05-r-ethereum.md· markdown
117 
118- Don't lead with "AI agents pay USDC." That triggers the "this is a vibes-not-tech post" pa
… (11 chars elided on L118)
119- Don't mention ICOs, tokens, "Web3 [thing]", or anything that smells like crypto-marketing
120- DO mention specific contract addresses, EIP numbers, gas considerations, latency benchmark
… (1 chars elided on L120)
121- DO acknowledge alternative L2s and chains — implying Ethereum mainnet is the only option w
… (16 chars elided on L121)
Occurrences
1 occurrence · at L119
How to fix
Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.
  1. Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
  2. Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-IMPERATIVE-01sha256dd0131c08d31efc2rubric 365aacaView on GitHub
Supply chainscore 100 · 0 findings
All supply chain checks passedNo findings in this category for the latest scan.pass
Maintenancescore 100 · 0 findings
All maintenance checks passedNo findings in this category for the latest scan.pass
Transparencyscore 100 · 0 findings
All transparency checks passedNo findings in this category for the latest scan.pass
Communityscore 100 · 0 findings
All community checks passedNo findings in this category for the latest scan.pass
Vendor response · right of reply
Are you the maintainer? Submit a response →

Audit the pieces. Scan the whole. Decide.

~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.