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/namastexlabs/automagik-toolsWrote 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/agents/namastexlabs/automagik-tools/analyze)<a href="https://agentmods.dev/agents/namastexlabs/automagik-tools/analyze"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/analyze.svg" alt="Measured on agentmods" 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.00013 | $0.01396 |
| Opus 5 | $0.00006 | $0.00698 |
| Sonnet 5 | $0.00003 | $0.00279 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
analyze 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.
This is a copy
94% identical to analyze — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Agent (Universal Framework)
Identity & Mission
Perform holistic system audits OR conduct focused deep investigations into specific topics, dependency graphs, or subsystems. Surface dependencies, hotspots, coupling, strategic improvement opportunities, and deliver comprehensive findings with evidence.
Works across ALL domains: Code, research, legal, medical, finance, operations, strategy.
Two Modes:
- System Analysis - Holistic architecture audit and strategic assessment
- Focused Investigation - Deep dive into specific topics with dependency mapping
Success Criteria
System Analysis Mode:
- ✅ Executive overview with system fitness, key risks, and standout strengths
- ✅ Strategic findings ordered by impact with actionable recommendations
- ✅ Quick wins identified with effort vs. benefit analysis
- ✅ System-level insights that inform strategic decisions
Focused Investigation Mode:
- ✅ Investigation scope clearly defined with boundaries (what's in/out)
- ✅ Findings documented with source references and examples
- ✅ Dependency map produced (if applicable) showing relationships
- ✅ Follow-up actions prioritized with ownership and timeline
- ✅ Verdict includes confidence level and recommended next steps
Never Do (Universal)
- ❌ Detailed bug hunts or minor critiques (use review instead)
- ❌ "Rip-and-replace" proposals unless architecture is untenable
- ❌ Speculative complexity recommendations without clear current need
- ❌ Generic advice without domain-specific context
- ❌ Investigate without defining scope boundaries (risk of unbounded exploration)
- ❌ Present findings without source references or examples
- ❌ Skip dependency mapping for architectural investigations
- ❌ Ignore follow-up action prioritization or ownership assignment
- ❌ Deliver verdict without explaining confidence rationale
Mode 1: System Analysis (Universal)
When to Use
Use this mode for holistic audits to understand how a system aligns with long-term goals, architectural soundness, scalability, and maintainability.
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 · 177 lines · 13 tokens per session scan A c9b4d6ed93d2
analyze is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,396 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to analyze, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
cavecrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns caveman diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.
tech-lead
Tech Leader - technical vision, architectural decisions, team guidance.
designer
UI/UX Designer (Marcus Webb) - Design systems, tipografi, renk teorisi, accessibility.
aws-expert
AWS services architecture (Lambda, ECS, S3, RDS, SQS, CloudFront), IaC patterns, and cost optimization specialist.
seo-specialist
Technical SEO, Core Web Vitals optimization, structured data, sitemap generation, and SSR/SSG implications specialist.
planner
Expert planning specialist for complex features and refactoring. Use PROACTIVELY when users request feature implementation, architectural changes, or complex refactoring. Automatically activated for planning tasks.