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/norkzyt/claude-code-autopilot/c-progit clone --depth 1 https://github.com/NorkzYT/claude-code-autopilotWrote 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/norkzyt/claude-code-autopilot/c-pro)<a href="https://agentmods.dev/agents/norkzyt/claude-code-autopilot/c-pro"><img src="https://agentmods.dev/badge/agents/norkzyt/claude-code-autopilot/c-pro.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.00047 | $0.00245 |
| Opus 5 | $0.00023 | $0.00122 |
| Sonnet 5 | $0.00009 | $0.00049 |
| Haiku 4.5 | $0.00005 | $0.00024 |
Grade A, and why
c-pro 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 36 lines · 47 tokens per session scan A 1ac8473f5321
c-pro is an agent published in the GitHub repository NorkzYT/claude-code-autopilot (2 stars, last pushed 2mo ago), licensed GPL-3.0. It adds 47 tokens to every session and 245 once invoked, about $0.0002 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-31.
Other agents, from other repositories
arm-cortex-expert
Senior embedded software engineer specializing in firmware and driver development for ARM Cortex-M microcontrollers (Teensy, STM32, nRF52, SAMD). Decades of experience writing reliable, optimized, and maintainable embedded code with deep expertise in memory barriers, DMA/cache coherency, interrupt-driven I/O, and…
c-cpp-expert-agent
Deep C++ expertise for template metaprogramming, SFINAE, constexpr, type traits, and memory model questions in embedded context.
memory-audit-agent
Audits embedded code for stack overflow, heap fragmentation, memory leaks, and allocation patterns on constrained devices.
rust-engineer
Use when building Rust systems where memory safety, ownership patterns, zero-cost abstractions, and performance optimization are critical for systems programming, embedded development, async applications, or high-performance services.
c-pro
Write efficient C code with proper memory management, pointer arithmetic, and system calls. Handles embedded systems, kernel modules, and performance-critical code. Use PROACTIVELY for C optimization, memory issues, or system programming.
c-systems-programmer
C programming specialist for systems programming, embedded systems, memory management, and performance optimization. Use when writing/reviewing C code, debugging memory leaks, investigating segfaults, working with POSIX APIs, implementing pthreads, optimizing embedded systems, using GDB/Valgrind debuggers, developing…