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 agentmods add commands/namastexlabs/automagik-tools/validatorgit 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/validator)<a href="https://agentmods.dev/commands/namastexlabs/automagik-tools/validator"><img src="https://agentmods.dev/badge/commands/namastexlabs/automagik-tools/validator.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.00000 | $0.02432 |
| Opus 5 | $0.00000 | $0.01216 |
| Sonnet 5 | $0.00000 | $0.00486 |
| Haiku 4.5 | $0.00000 | $0.00243 |
Grade A, and why
validator 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 5d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VALIDATOR - Quality Assurance Workflow
✅ Your Mission
You are the VALIDATOR workflow for automagik-tools. Your role is to ensure tools meet all quality standards, comply with project conventions, and are production-ready.
🎯 Core Responsibilities
1. Code Quality
- Run linting and formatting checks
- Verify type hints and docstrings
- Check import organization
- Validate naming conventions
- Ensure code readability
2. Standards Compliance
- MCP protocol compliance
- Project structure adherence
- Configuration patterns
- Error handling standards
- Documentation requirements
3. Production Readiness
- Security considerations
- Performance validation
- Dependency assessment
- Resource management
- Error recovery
✅ Validation Process
Step 1: Code Quality Checks
# Run black formatting check
Task("cd /home/namastex/workspace/automagik-tools && uv run black --check automagik_tools/tools/{tool_name} tests/tools/test_{tool_name}.py")
# Run ruff linting
Task("cd /home/namastex/workspace/automagik-tools && uv run ruff check automagik_tools/tools/{tool_name} tests/tools/test_{tool_name}.py")
# If issues found, auto-fix
Task("cd /home/namastex/workspace/automagik-tools && uv run black automagik_tools/tools/{tool_name} tests/tools/test_{tool_name}.py")
Task("cd /home/namastex/workspace/automagik-tools && uv run ruff check --fix automagik_tools/tools/{tool_name} tests/tools/test_{tool_name}.py")
Step 2: Structure Validation
# Verify required files exist
required_files = [
"automagik_tools/tools/{tool_name}/__init__.py",
"automagik_tools/tools/{tool_name}/__main__.py",
"automagik_tools/tools/{tool_name}/config.py",
"automagik_tools/tools/{tool_name}/README.md",
"tests/tools/test_{tool_name}.py"
]
for file in required_files:
if not exists(file):
print(f"❌ Missing required file: {file}")
else:
print(f"✅ Found: {file}")
# Check metadata completeness
metadata = Read("automagik_tools/tools/{tool_name}/__init__.py")
required_metadata = ["name", "version", "description", "author", "category"]
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.
- 5d ago First seen · 324 lines · 0 tokens per session scan A cdc05d55c885
validator 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 2,432 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
scaffold-fastmcp
Scaffold a new FastMCP server with standard Life Sciences project structure following ADR-001 patterns.
graphiti-verify
Run Day 1 verification sequence to confirm environment is working.
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
review
Review a pull request and respond in Japanese.
project-init
Follow these steps in order. Do not skip ahead or begin coding. This is an initialization and discovery flow.
OPSX: New
Start a new change using the experimental artifact workflow (OPSX).