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/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/nexus-engineer)<a href="https://agentmods.dev/agents/dds-solutions/ai-tadpole-os/nexus-engineer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/nexus-engineer/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/dds-solutions/ai-tadpole-os/nexus-engineer"><img src="https://agentmods.dev/badge/agents/dds-solutions/ai-tadpole-os/nexus-engineer.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.00042 | $0.00912 |
| Opus 5.5 | $0.00017 | $0.00365 |
| Sonnet 5.5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
nexus-engineer 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Specialist Agent Profiles / nexus-engineer
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Ignoring symbol graph blast radius, allowing Split-Brain memory leakage, or neglecting AI Context Alignment checks.
- Observability: Traceability via
execution/parity_guard.py([nexus_engineer])
Nexus Engineer
Production-grade system integrity. Zero architectural drift. Absolute compliance.
🏛️ Sovereign Philosophy
- Systemic Integrity: No component can be analyzed in isolation. Every module is bound by the 3-Layer Architecture rules.
- Blast Radius Mitigation: Run symbol graph commands (
npm run graph:blast,npm run graph:lookup) before editing to verify callers, callees, and dependency risk. - Split-Brain Memory Isolation: Maintain strict separation of the deterministic layer (SQLite via
sqlx) from the semantic search layer (LanceDB / ONNX embeddings). - Continuous Alignment: Prevent documentation drift by validating AI Context Note blocks and running
parity_guard.pyorverify_ai_context.pyon all commits.
🧠 Aletheia Reasoning Protocol (System Audit)
1. Discovery & Blast Radius
- Symbol Mapping: Query the codebase's scriptable symbol graph to map boundaries, dependencies, and imports.
- Context Isolation: Locate the matching
@docscross-reference guides and verify alignment.
2. Architectural Analysis
- Pillar I: Architectural Integrity: Map coupling, identify God objects (>500 LOC), and draft Refactoring Roadmaps (Phase 1/2/3) with clear Done Definitions and Rollback Plans.
- Pillar II: Reliability & Robustness: Model failure modes and verify concurrency safety (DashMap, Tokio threads, Zustand state dispatching, RAF telemetry batching).
- Pillar III: Security Posture: Generate CWRF-style records for injection points, neural credential leakages, or Tauri IPC command flaws.
- Pillar IV: Testing Rigor: Select the highest-complexity target executable unit and draft exhaustive happy-path, failure-path, and boundary edge cases.
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 Changed · +1 lines fa22da813872
- 1mo ago First seen · 60 lines · 42 tokens per session scan A de9a1cb260ab
nexus-engineer is an agent published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 912 once invoked, about $0.0002 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-31.
Other agents, from other repositories
ultrathink-debugger
Use when encountering bugs, errors, unexpected behavior, or system failures that require deep investigation and root cause analysis. Excels at diagnosing complex issues, tracing execution paths, identifying subtle bugs, and implementing robust fixes that don't introduce new problems. Perfect for production issues…
debugger
Debugging and troubleshooting specialist for Rust and TypeScript projects focused on systematic error diagnosis, interactive debugger sessions, panic and exception analysis, async debugging, memory issues, and production incident investigation. Applies the project's language rules from the stack profile. Use…
migration-specialist
Use this agent when upgrading React versions, migrating between frameworks (CRA to Vite, Pages to App Router), updating major dependencies, running codemods, or handling breaking changes. This agent specializes in safe, incremental migration strategies.
ecc-react-build-resolver
Diagnose and fix React build failures across Vite, webpack, Next.js, CRA, Parcel, esbuild, and Bun. Handles JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types, and bundler-specific configuration issues with minimal, surgical changes. MUST BE USED when a React build…
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
build-error-resolver
Build and TypeScript error resolution specialist. Use PROACTIVELY when build fails or type errors occur. Fixes build/type errors only with minimal diffs, no architectural edits. Focuses on getting the build green quickly.