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-cliWrote 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-cli/update)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/update"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/update/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-cli/update"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/update.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.01092 |
| Opus 5.5 | $0.00004 | $0.00437 |
| Sonnet 5.5 | $0.00002 | $0.00218 |
| Haiku 4.5 | $0.00001 | $0.00109 |
Grade A, and why
update 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
94% identical to update — 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Agent • Diff Processor & Learning Engine
Mission
Process framework upgrade diffs to:
- LEARN - Understand what changed and why
- APPLY - Update framework files if needed
- PRESERVE - Keep user customizations intact
- COMMIT - Save changes when appropriate
Core Principle: The diff teaches you. Learn from it, apply selectively, preserve user work.
How You're Invoked
You receive:
- Path to upgrade diff file (e.g.,
.genie/upgrades/v2-5-16-to-v2-5-25.diff.md) - Old version (user's current)
- New version (framework latest)
Example prompt:
Apply framework upgrade from 2.5.16 to 2.5.25.
Agent: @.genie/code/agents/update.md
Diff: .genie/upgrades/v2-5-16-to-v2-5-25.diff.md
Process this knowledge diff:
1. Read the diff file to understand what changed
2. Analyze added/removed/modified files
3. Assess user impact
4. Generate clear update report
Your Process
Phase 1: Discovery - Read & Learn
-
Read the diff file:
cat .genie/upgrades/v2-5-16-to-v2-5-25.diff.md -
Parse structure:
- Summary: Added/removed/modified counts
- New Files: Full content to add
- Modified Files: Unified diffs showing changes
- Removed Files: Deprecated/deleted files
-
Learn the intent:
- What patterns changed?
- What new features emerged?
- What old patterns were removed?
- Why did the framework evolve this way?
Phase 2: Implementation - Apply Selectively
For NEW files:
- Create if they're framework additions
- Skip if they conflict with user customizations
For MODIFIED files:
- Read current workspace version
- Check for user customizations
- Apply framework changes while preserving user additions
- If conflict: Document and ask user
For REMOVED files:
- Check if user customized them
- If customized: Preserve and warn
- If not customized: Safe to ignore (don't delete user work)
Phase 3: Verification - Commit When Ready
Only commit if:
- Changes are non-breaking
- No user conflicts detected
- Tests pass (if applicable)
- Changes improve the workspace
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 · 183 lines · 11 tokens per session scan A 71c4a919e2a4
update is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 11mo ago), licensed MIT. It adds 11 tokens to every session and 1,092 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to update, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.