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/arch3rPro/ark-spaceWrote 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/arch3rpro/ark-space/code-engineer)<a href="https://agentmods.dev/agents/arch3rpro/ark-space/code-engineer"><img src="https://agentmods.dev/badge/agents/arch3rpro/ark-space/code-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/arch3rpro/ark-space/code-engineer"><img src="https://agentmods.dev/badge/agents/arch3rpro/ark-space/code-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.00016 | $0.00328 |
| Opus 5.5 | $0.00006 | $0.00131 |
| Sonnet 5.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 1mo 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.
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.
- 1mo ago 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 1mo ago), licensed MIT. It adds 16 tokens to every session and 328 once invoked, about $0.0001 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
ckm-scout
Use this agent when the user wants to search the openEHR Clinical Knowledge Manager (CKM) aggressively for reusable archetypes before authoring a new one. Enforces the reuse-first principle by running parallel searches with varied phrasings and returning a ranked reuse/specialize/new recommendation. Invoke proactively…
spec-researcher
Use this agent when the user needs a grounded answer from openEHR specifications (Reference Model, Archetype Model, AQL, BASE, ITS-REST, LANG, CDS, etc.) that isn't already in an MCP guide digest. Uses the howto/spec-lookup methodology — llms.txt site index, Markdown twin URLs, and BMM-backed typespecificationget — to…
clinical-modeler
Use this agent when the user needs to read, write, review, or edit local archetype (.adl), template (.oet, Archetype Designer .t.json, .opt), or composition files in the workspace. It writes only to the local workspace, and can perform read-only MCP lookups (terminology resolution, RM/AM type specs, guides, and…
planner
Receives a requirement and produces a structured development plan with subtask decomposition.
dev
Implements features based on a development plan, and fixes bugs reported by the test agent.
learner
Learns from completed dev-test cycles and extracts reusable knowledge to avoid repeated pitfalls.