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/flint.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/flint)<a href="https://agentmods.dev/agents/myicor/mypka/flint"><img src="https://agentmods.dev/badge/agents/myicor/mypka/flint/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/flint"><img src="https://agentmods.dev/badge/agents/myicor/mypka/flint.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.00074 | $0.00242 |
| Opus 5.5 | $0.00030 | $0.00097 |
| Sonnet 5.5 | $0.00015 | $0.00048 |
| Haiku 4.5 | $0.00007 | $0.00024 |
Grade A, and why
flint 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 Flint. Your canonical contract is
06 AI Team/Agents/Flint/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/Flint/Flint.md. Re-read your own
06 AI Team/Agents/Flint/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/Flint/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 First seen · 15 lines · 74 tokens per session scan A a960099159b2
flint is an agent published in the GitHub repository myICOR/myPKA (318 stars, last pushed 22d ago), licensed MIT. It adds 74 tokens to every session and 242 once invoked, about $0.0003 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-09-26.
Other agents, from other repositories
jd-fix-agent
You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.
pr-reviewer
Use this agent when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR #N", or provides a GitHub PR URL for review. Examples:\n\n \nContext: User wants to review the PR for the current branch\nuser: "review this pr"\nassistant: "I'll use the pr-reviewer agent to find…
pr-comment-resolver
Use this agent when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", or "respond to PR review". Examples: Context: User has received review feedback on their PR user: "address the PR comments on #42" assistant: "I'll use the pr-comment-resolver agent to analyze and…
debugger
Debugging specialist for root cause analysis, investigating defects, and tracing execution flow. Use when encountering bugs, test failures, or unexpected behavior that requires systematic investigation. For example: tracing a null pointer exception, analyzing intermittent test failures, or debugging race conditions.
performance_engineer
Performance engineering specialist for bottleneck identification, profiling, and optimization. Use when the task requires performance analysis, load testing setup, memory profiling, or algorithmic optimization. For example: profiling CPU hotspots, reducing memory allocations, or optimizing database query plans.
refactor
Refactoring specialist for codebase modernization, structural improvements, and technical debt reduction. Use when the task involves reorganizing code, extracting abstractions, renaming for clarity, or migrating to new patterns. For example: extracting a service layer, converting callbacks to async/await, or splitting…