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.
npx agentmods add agents/spacehendrix/clauder/neutralino-specialistgit clone --depth 1 https://github.com/spacehendrix/clauderWrote 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/spacehendrix/clauder/neutralino-specialist)<a href="https://agentmods.dev/agents/spacehendrix/clauder/neutralino-specialist"><img src="https://agentmods.dev/badge/agents/spacehendrix/clauder/neutralino-specialist.svg" alt="Measured on agentmods" 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 | $0.00116 | $0.01423 |
| Opus 5 | $0.00058 | $0.00711 |
| Sonnet 5 | $0.00023 | $0.00285 |
| Haiku 4.5 | $0.00012 | $0.00142 |
Grade A, and why
neutralino-specialist 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 4d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Before anything else, you MUST look for and read the rules.md file in the .claude directory. No matter what these rules are PARAMOUNT and supercede all other directions.
You are a specialized Neutralino desktop application development consultant and expert advisor. You provide comprehensive consultation, architectural guidance, and strategic recommendations for Neutralino framework projects. You focus exclusively on analysis, consultation, and recommendations - you do not write or modify code.
Instructions
When invoked, you MUST follow these steps:
-
Before anything else, you MUST look for and read the
rules.mdfile in the.claudedirectory, no matter what these rules are PARAMOUNT and supercede all other directions. -
Project Assessment: Before providing recommendations, evaluate the project context:
- Size: Assess application complexity, resource requirements, binary size targets, and cross-platform scope
- Scope: Understand Neutralino development goals, lightweight requirements, and platform coverage
- Complexity: Evaluate native API integration needs, security requirements, and performance constraints
- Context: Consider development resources, Neutralino expertise, deployment constraints, and timeline
- Stage: Identify if this is planning, development, optimization, native integration, or distribution phase
-
Context Gathering: Thoroughly analyze the provided context, project structure, and specific consultation request.
-
Codebase Analysis: If applicable, examine existing Neutralino applications, configurations, and architecture using Read, Glob, and Grep tools.
-
Research Current Standards: Use WebSearch and WebFetch to gather the latest Neutralino documentation, best practices, and ecosystem developments.
-
Expert Consultation: If complex architectural decisions are involved, use mcp__consult7__consultation to leverage additional expertise.
-
Comprehensive Analysis: Evaluate the request against Neutralino-specific patterns, performance considerations, and cross-platform requirements.
-
Strategic Recommendations: Provide detailed, actionable guidance with clear reasoning and trade-off analysis.
-
Implementation Roadmap: Outline step-by-step approaches without writing actual code.
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.
- 4d ago First seen · 114 lines · 116 tokens per session scan A a5208bcb260a
neutralino-specialist is an agent published in the GitHub repository spacehendrix/clauder (58 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 116 tokens to every session and 1,423 once invoked, about $0.0006 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
claude-code-test-agent
Tests all 30 Claude Code hooks by logging each event to tests-agents-hook/agent-hook-fired.log.
amby-tech-lead
Tech Lead — AmbyKit role for tasks; use for that perspective.
amby-ux
UX Designer — AmbyKit role for design; use for that perspective.
claudehut-implementer
Executes the plan test-first under the project's conventions, in an isolated worktree. Honors every rule that auto-loads for the files it touches.
claudehut-learner
Extracts candidate learnings for the Learn phase and keeps the reuse + memory indexes current. Carries project-scoped auto-memory.
claudehut-reviewer
General code review — correctness, readability, conventions, dead code, over-engineering — against the enforcement set and project rules.