automagik-tools: Command for Claude Code

.claude/commands/README.md

README is a command for Claude Code from namastexlabs/automagik-tools. It costs 0 tokens per session (1,918 once invoked), scanned A, original, Apache-2.0.

A directory of automated workflows for developing MCP tools. MCP, or Model Context Protocol, is a way for an AI agent to use tools that connect to outside services.

In plain words
What is it for?
Use it to coordinate the creation of MCP tools, from analysing requirements through building, testing, quality checks, packaging, and deployment.
Why use it?
It separates tool development into focused stages, making requirements, implementation, testing, validation, deployment, and publishing easier to manage.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is namastexlabs/automagik-tools's own configuration. It tells Claude Code how to work on automagik-tools itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything automagik-tools configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/namastexlabs/automagik-tools/main/.claude/commands/README.md
Clone the repo
git clone --depth 1 https://github.com/namastexlabs/automagik-tools

Made for: Claude Code.

Wrote 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.

agentmods badge for README

README.md
[![agentmods](https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/readme/github.svg)](https://agentmods.dev/commands/namastexlabs/automagik-tools/readme)
Your own site
<a href="https://agentmods.dev/commands/namastexlabs/automagik-tools/readme"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/readme/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.

agentmods 80×15 button for README

Your own site · 80×15
<a href="https://agentmods.dev/commands/namastexlabs/automagik-tools/readme"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/readme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01918
Opus 5 $0.00000 $0.00959
Sonnet 5 $0.00000 $0.00384
Haiku 4.5 $0.00000 $0.00192

Measured 9d ago against content hash 5975863d5d1a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

README 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 9d 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.

.claude/commands/README.md · 353 lines

How it starts

The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AutoMagik Tools Automated Development Workflows

Overview

This directory contains specialized workflows for automated MCP tool development. Each workflow focuses on a single aspect of the development lifecycle, enabling rapid creation of high-quality MCP tools with minimal human intervention.

Workflow System Architecture

Core Philosophy

  • Ultra-Specialization: Each workflow does ONE thing perfectly
  • Linear Integration: Project management through Linear issues
  • Memory-Driven: Learn from every tool creation
  • Pattern Reuse: >80% code reuse from existing tools
  • Quality First: Automated testing and validation

Available Workflows

  1. ORCHESTRATOR - Project management and workflow coordination
  2. ANALYZER - Requirements analysis and planning
  3. BUILDER - Tool implementation and coding
  4. TESTER - Comprehensive testing and coverage
  5. VALIDATOR - Quality assurance and compliance
  6. DEPLOYER - Package, deploy, and publish

Quick Start

Creating a New MCP Tool

To create a new tool, use the ORCHESTRATOR workflow:

Create a new MCP tool for [API/Service Name] that [description of functionality].
API documentation: [OpenAPI spec URL or documentation link]
Authentication: [auth method - API key, OAuth, etc.]
Priority: [high/medium/low]

Example:

Create a new MCP tool for Discord API that enables message management and channel operations.
API documentation: https://discord.com/developers/docs/reference
Authentication: Bot token
Priority: high

Workflow Execution Flow

graph TD
    A[ORCHESTRATOR] --> B[ANALYZER]
    B --> C[BUILDER]
    C --> D[TESTER]
    D --> E[VALIDATOR]
    E --> F[DEPLOYER]
    
    A --> G[Linear Epic]
    G --> H[Sub-tasks for each workflow]
    
    B --> I[Memory: Patterns]
    C --> I
    D --> I
    E --> I
    F --> I

Detailed Workflow Guide

1. ORCHESTRATOR Workflow

Purpose: Coordinate all workflows and manage the development epic

Read the full file on GitHub · 353 lines

Changes

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.

  1. 9d ago First seen · 353 lines · 0 tokens per session scan A 5975863d5d1a

Subscribe to this mod's changes

README is a command published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 9mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,918 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.