Borrowing it
Nothing to install: this file belongs to namastexlabs/automagik-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-tools/main/.claude/commands/analyzer.mdgit 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/commands/namastexlabs/automagik-tools/analyzer)<a href="https://agentmods.dev/commands/namastexlabs/automagik-tools/analyzer"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/analyzer/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/commands/namastexlabs/automagik-tools/analyzer"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/analyzer.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.00000 | $0.01642 |
| Opus 5.5 | $0.00000 | $0.00657 |
| Sonnet 5.5 | $0.00000 | $0.00328 |
| Haiku 4.5 | $0.00000 | $0.00164 |
Grade A, and why
analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ANALYZER - Requirements Analysis Workflow
🔍 Your Mission
You are the ANALYZER workflow for automagik-tools. Your role is to analyze requirements, examine existing patterns, and create detailed implementation plans for new MCP tools.
🎯 Core Responsibilities
1. Requirements Analysis
- Parse OpenAPI specifications
- Extract key functionality and endpoints
- Identify authentication methods
- Determine data models and parameters
- Assess complexity and scope
2. Pattern Recognition
- Search existing tools in
automagik_tools/tools/ - Identify similar implementations
- Extract reusable patterns
- Document best practices found
- Note potential pitfalls
3. Implementation Planning
- Create detailed technical specification
- Define tool structure and components
- Specify configuration requirements
- Plan testing strategy
- Estimate implementation effort
📋 Analysis Process
Step 1: Gather Requirements
# Check if OpenAPI spec provided (automagik-tools has built-in OpenAPI support)
if [[ -n "$OPENAPI_URL" ]]; then
# Fetch and analyze OpenAPI spec
WebFetch(url="$OPENAPI_URL", prompt="Extract: title, endpoints, auth methods, data models")
# Note: automagik-tools supports direct OpenAPI deployment:
# uvx automagik-tools openapi https://api.example.com/openapi.json
fi
# Understand the tool's purpose
# Document key features and capabilities
Step 2: Examine Existing Tools
# List current tools (correct absolute path)
LS("/home/namastex/workspace/automagik-tools/automagik_tools/tools")
# Find similar tools by searching implementations
Grep(pattern="FastMCP|create_server|get_metadata", path="automagik_tools/tools/")
# Read actual working tool implementations
Read("/home/namastex/workspace/automagik-tools/automagik_tools/tools/automagik/__init__.py")
Read("/home/namastex/workspace/automagik-tools/automagik_tools/tools/automagik/config.py")
Read("/home/namastex/workspace/automagik-tools/automagik_tools/tools/genie/__init__.py")
Read("/home/namastex/workspace/automagik-tools/automagik_tools/tools/genie/config.py")
# Check testing patterns from actual tests
Read("/home/namastex/workspace/automagik-tools/tests/tools/test_automagik_agents.py")
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 · 227 lines · 0 tokens per session scan A ca25acffb548
analyzer is a command published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 10mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,642 tokens. 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 commands, from other repositories
api-mock
Build realistic API mock servers with request stubbing, dynamic data, test scenarios, and contract testing.
symfony-cache
Implement caching strategies using Symfony Cache component.
api-docs.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
openui-integrate
Wire up the LLM backend — the core integration command.
p3-data-model
Designs the Data Model with entities and relationships as well as the API design with interface specification. The result is DATAMODEL.md and APISPEC.md as the binding foundation for implementation.
dare-layered-design
Enforce arquitetura estrita de 4 camadas (Handlers, Services, Repositories, Models) em projetos DARE — independente de linguagem.