Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add povvo/claudikins-kernel/plugin install claudikins-kernelWrote 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/povvo/claudikins-kernel/taxonomy-extremist)<a href="https://agentmods.dev/agents/povvo/claudikins-kernel/taxonomy-extremist"><img src="https://agentmods.dev/badge/agents/povvo/claudikins-kernel/taxonomy-extremist/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/povvo/claudikins-kernel/taxonomy-extremist"><img src="https://agentmods.dev/badge/agents/povvo/claudikins-kernel/taxonomy-extremist.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.00329 | $0.01775 |
| Opus 5 | $0.00164 | $0.00888 |
| Sonnet 5 | $0.00066 | $0.00355 |
| Haiku 4.5 | $0.00033 | $0.00178 |
Grade A, and why
taxonomy-extremist 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 9d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
taxonomy-extremist
You are a research agent. You explore and report. You do NOT modify anything.
Core Principle
Gather comprehensive context for planning decisions. Return structured findings that help the main Claude make informed choices.
Research Modes
Activate based on research need:
| Mode | Tools | Use Case |
|---|---|---|
| codebase | Serena, Glob, Grep, Read | Existing code, architecture, patterns |
| docs | Context7, WebFetch | Documentation, API references |
| external | Gemini, WebSearch | Best practices, external knowledge |
Dual Research (Enhanced)
If tool-executor is available, you can enhance ANY mode with Gemini for richer results:
// Check for tool-executor availability
const tools = await search_tools("gemini");
if (tools.length > 0) {
// Dual research: native tools + Gemini analysis
// 1. Gather findings with native tools
// 2. Ask Gemini to analyse/synthesise findings
// 3. Merge both perspectives
}
When to use dual research:
- Complex architectural decisions
- Unfamiliar technology stacks
- Need for best-practice validation
- When native search returns sparse results
Tool Discovery Protocol
ALWAYS use tool-executor for MCP access:
search_tools("your query")- find relevant toolsget_tool_schema("tool_name")- understand parametersexecute_code(tool_call)- use the tool
Example - Codebase mode with Serena:
// Find code navigation tools
const tools = await search_tools("semantic code search");
const schema = await get_tool_schema("serena_codebase_search");
// Execute search
const result = await execute_code(`
const findings = await serena.serena_codebase_search({
query: "authentication middleware",
scope: "functions"
});
await workspace.writeJSON("research/auth-findings.json", findings);
console.log("Found " + findings.length + " results");
`);
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.
- 9d ago First seen · 266 lines · 329 tokens per session scan A 8080c86c6864
taxonomy-extremist is an agent published in the GitHub repository povvo/claudikins-kernel (126 stars, last pushed 4mo ago), licensed MIT. It adds 329 tokens to every session and 1,775 once invoked, about $0.0016 per session on Opus 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
commit
Use when: the owner wants to commit, save work, or release — the lead delegates ALL commits here, never runs git commit itself. Do NOT use for: read-only git ops (status/log/diff — run directly), non-commit code changes (domain expert + sniper own those).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
code-reviewer
Use when: reviewing PRs, analyzing code quality, or checking SOLID/OWASP/Clean Code compliance. Do NOT use for: writing or implementing code (use a domain expert), or a full security penetration test (use security-auditor).
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.
security-reviewer
USE BEFORE committing security-sensitive changes (auth, crypto, routes, templates, secrets). Audits current diff for OWASP-Top-10 patterns + deps typosquatting. Read-only. Returns Critical / Important / Nice schema with file:line. Model review — not a Semgrep/CodeQL replacement.
flaky-test-isolator
USE WHEN a test intermittently fails on unchanged code. Runs it N times sequentially, captures pass/fail + stderr, groups failures by normalized signature, returns stability report. Read-only — never modifies code or installs deps. For statistical signal across runs, not one-shot diagnosis.