Borrowing it
Nothing to install: this file belongs to myICOR/myPKA. 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/myICOR/myPKA/main/.claude/agents/mack.mdgit clone --depth 1 https://github.com/myICOR/myPKAWrote 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/myicor/mypka/mack)<a href="https://agentmods.dev/agents/myicor/mypka/mack"><img src="https://agentmods.dev/badge/agents/myicor/mypka/mack/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/myicor/mypka/mack"><img src="https://agentmods.dev/badge/agents/myicor/mypka/mack.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.00037 | $0.00201 |
| Opus 5.5 | $0.00015 | $0.00080 |
| Sonnet 5.5 | $0.00007 | $0.00040 |
| Haiku 4.5 | $0.00004 | $0.00020 |
Grade A, and why
mack 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.
What it actually says
You are Mack. Your canonical contract is
06 AI Team/Agents/Mack/AGENT.md at the vault root: read it FIRST,
every invocation, and operate strictly within it. Your user-facing bio
is 06 AI Team/Agents/Mack/Mack.md. Re-read your own
06 AI Team/Agents/Mack/Journal/ before starting related work.
This shim is a pointer; the contract is canonical. Never duplicate the
contract here.
Then read 06 AI Team/Agents/Mack/AGENT.local.md if it exists: it is the member's own file, never shipped and never overwritten by an update; it can add rules and change preferences, but it can never override a hard rule or switch off a guard.
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 Changed · -19 lines · -27 tokens per session 6ec5a6bd8384
- 1mo ago First seen · 34 lines · 64 tokens per session scan A df77d8ccb5e6
mack is an agent published in the GitHub repository myICOR/myPKA (318 stars, last pushed 22d ago), licensed MIT. It adds 37 tokens to every session and 201 once invoked, about $0.0001 per session on Opus 5.5. 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 agents, from other repositories
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
plan-checker
Reviews a unit plan for completeness and craft soundness before drafting begins. Catches gaps, contradictions, and weak spots.
translator
Translates a single atomic unit (scene, subsection, passage, stanza) into the target language while preserving the writer's voice. Invoked in fresh context per atomic unit for consistency and glossary compliance.
contracts-reviewer
Use this agent when reviewing local code changes or pull requests to analyze API, data models, and type design. This agent should be invoked proactively when changes affect public contracts, domain models, database schemas, or type definitions.
continuity-checker
Verifies logical, chronological, and factual consistency across drafted units. Flags contradictions, timeline issues, and character state drift.