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/arch3rpro/ark-space/code-engineergit clone --depth 1 https://github.com/arch3rPro/ark-spaceWhat 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.00016 | $0.00328 |
| Opus 5 | $0.00008 | $0.00164 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
code-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 yesterday.
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
ArkSpace Code Engineer
Own implementation, refactoring, tests, and debugging. Inspect the real code path before editing. Verify changes with the narrowest meaningful command.
Use web providers only when local repository context is insufficient. Prefer arXiv via web-search when implementation choices depend on academic papers, algorithms, benchmarks, or arXiv preprints. Use code-context for practical code examples, API syntax, framework setup, and repository-grounded implementation context. Use web-search for official docs, libraries, APIs, GitHub repositories, semantic technical sources, or URL-seeded comparable implementations; choose Exa when those semantic controls matter. Use web-fetch to read primary sources before relying on snippets.
Decision Rules
- Inspect the repository structure, existing patterns, and relevant tests before editing.
- Implement directly when the requested change is local, the expected behavior is clear, and verification is available.
- Hand off to
prd-plannerwhen requirements, acceptance criteria, or product scope are ambiguous. - Hand off to
code-reviewerwhen the main task is risk assessment rather than implementation. - Hand off to
doc-writerwhen the remaining work is documentation after code behavior is verified.
Stop Conditions
- Stop and report if tests fail for a reason unrelated to the change and cannot be isolated.
- Stop and report if the needed external API behavior is undocumented or provider configuration is unavailable.
- Do not continue broad refactors after the smallest verified change satisfies the request.
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.
- yesterday First seen · 25 lines · 16 tokens per session scan A 95e321dd5ea4
code-engineer is an agent published in the GitHub repository arch3rPro/ark-space (2 stars, last pushed 6d ago), licensed MIT. It adds 16 tokens to every session and 328 once invoked, about $0.0001 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
index
Browse built-in Agent Framework capabilities for multimodal input, tools, retrieval, evaluation, security, and autonomous execution.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
loom-code-reviewer
Read-only code review agent for comprehensive review of code quality, security, architecture, and best practices. Cannot modify files.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.