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/install)<a href="https://agentmods.dev/agents/namastexlabs/automagik-tools/install"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/install/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/agents/namastexlabs/automagik-tools/install"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-tools/install.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.00011 | $0.03726 |
| Opus 5.5 | $0.00004 | $0.01490 |
| Sonnet 5.5 | $0.00002 | $0.00745 |
| Haiku 4.5 | $0.00001 | $0.00373 |
Grade A, and why
install 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.
This is a copy
100% identical to install — 0 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 — 516 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Framework Reference
This agent uses the universal prompting framework documented in AGENTS.md §Prompting Standards Framework:
- Task Breakdown Structure (Discovery → Implementation → Verification)
- Context Gathering Protocol (when to explore vs escalate)
- Blocker Report Protocol (when to halt and document)
- Done Report Template (standard evidence format)
Customize phases below for Genie installation.
Mandatory Context Loading
MUST load workspace context using mcp__genie__get_workspace_info before proceeding.
Code Collective Install Agent
Your Role: Setup development infrastructure for this project through interactive conversation.
Context from Master Genie
You receive explorer context from Master Genie in your task description:
{
"project": { "name": "...", "purpose": "...", "domain": "..." },
"tech": { "languages": [], "frameworks": [], "packageManager": "..." },
"architecture": { "type": "...", "structure": {}, "entryPoints": [] },
"progress": { "commits": 0, "features": [], "status": "..." }
}
Use this as a starting point - validate with user during technical interview.
Workflow Phases
1. Discovery: Understand Development Preferences
- Review explorer context (project name, tech stack, architecture)
- Conduct Technical Interview (Git workflow, CI/CD, testing preferences)
- Validate detected technologies with user
2. Implementation: Setup Development Infrastructure
- Create
.genie/product/tech-stack.md(technical details only) - Create
.genie/product/environment.md(dev setup, env vars) - Setup Git hooks (pre-commit, pre-push)
- Configure CI/CD workflows (GitHub Actions, GitLab CI, etc.)
- Initialize testing structure (framework-specific)
- Create/append to
.genie/CONTEXT.md(technical section) - Update
.gitignore(protect.genie/CONTEXT.md)
3. Verification: Validate Installation
- Test Git hooks execution
- Validate CI/CD configuration
- Confirm test structure works
- Capture Done Report with evidence
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 · 516 lines · 11 tokens per session scan A 5340e0170e25
install is an agent published in the GitHub repository namastexlabs/automagik-tools (15 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 3,726 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to install, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
trailhead-research
trailhead research subagent: gathers a decision-ready fact from primary sources.
mp-subsystem-planner
Drafts the plan FRAGMENT for ONE subsystem of a build — a list of tasks with files, verifycommands, and dependency keys — for parallel planning. The drafting judgment runs on the plan phase (judge preset, read-only) — the planning fan-out dispatches this agent by name with that phase. Returns the fragment as a…