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.
npx skills add myclaude-sh/myclaude-creator-engine --skill aegisgit clone --depth 1 https://github.com/myclaude-sh/myclaude-creator-engineWrote 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/skills/myclaude-sh/myclaude-creator-engine/aegis)<a href="https://agentmods.dev/skills/myclaude-sh/myclaude-creator-engine/aegis"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/aegis/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/skills/myclaude-sh/myclaude-creator-engine/aegis"><img src="https://agentmods.dev/badge/skills/myclaude-sh/myclaude-creator-engine/aegis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.04594 |
| Opus 5 | $0.00032 | $0.02297 |
| Sonnet 5 | $0.00013 | $0.00919 |
| Haiku 4.5 | $0.00006 | $0.00459 |
Grade A, and why
aegis 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AEGIS — AI Code Auditor Security Skill
When to Use
- Audit codebase security before deployment or release
- Find vulnerabilities in code (SAST-style analysis)
- Security review of pull requests or new features
- Check compliance against OWASP, NIST, CIS, PCI DSS, SOC 2, ISO 27001, GDPR, HIPAA
- Harden project security (headers, validation, hooks, CI/CD)
- Fix security issues with auto/guided transforms
- Threat model an application using STRIDE
- Check for hardcoded secrets or credentials
- Review dependencies for known CVEs
- Generate security headers or Content Security Policy
When NOT to Use
- Runtime/dynamic testing (DAST) — AEGIS is static analysis only, not a runtime scanner
- Network penetration testing — use dedicated pentest tools (Burp, nmap, Metasploit)
- Physical security assessments — out of scope entirely
- Non-code projects — AEGIS needs source code to analyze
- Already-deployed incidents — use incident response tooling, not audit tooling
- Performance testing disguised as DoS checks — AEGIS flags DoS vectors, doesn't load-test
Question System
Before starting analysis, check for these inputs:
| Input | Required | If Missing |
|---|---|---|
| Project path / codebase | Yes | Use current working directory. If empty, ask: "Which project should I audit?" |
| Engagement mode (RAPID/STANDARD/DEEP) | No | Default to STANDARD. Infer RAPID if user says "quick check" or "PR review". Infer DEEP if "pre-release" or "full audit". |
| Specific focus area | No | Audit everything. If user mentions "auth", "uploads", "API", focus STRIDE on those entry points first. |
| Compliance frameworks needed | No | Default to OWASP Top 10. Add others if user mentions "SOC 2", "PCI", "HIPAA", etc. |
| Fix authorization | No | Always ask before applying auto-fixes. Never fix without confirmation. |
Boot Protocol
- Identify project: framework, language, stack from package.json/config files
- Select engagement mode based on user request:
- RAPID (<15 min): Secrets + deps + top 25 patterns. Use for PR review, quick checks.
- STANDARD (30-60 min): Full STRIDE + 300 patterns + compliance. Default for "audit my code."
- DEEP (2-4 hours): Full PASTA + attack trees + supply chain + all infra. Pre-release audits.
- Build Security Context Object (SCO): entry points, trust boundaries, data flows
- Execute the three cycles: AUDIT -> FIX -> HARDEN
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 388 lines · 63 tokens per session scan A 82f677d3cb77
aegis is a skill published in the GitHub repository myclaude-sh/myclaude-creator-engine (25 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 4,594 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
app-namer
Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
in-app-events
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.