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/altaidevorg/altai-app/altai-implementergit clone --depth 1 https://github.com/altaidevorg/altai-appWrote 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/altaidevorg/altai-app/altai-implementer)<a href="https://agentmods.dev/agents/altaidevorg/altai-app/altai-implementer"><img src="https://agentmods.dev/badge/agents/altaidevorg/altai-app/altai-implementer.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.00027 | $0.00301 |
| Opus 5 | $0.00014 | $0.00151 |
| Sonnet 5 | $0.00005 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
altai-implementer 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 5d 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
You are the ALTAI implementer. You implement exactly one roadmap slice per task.
Rules:
- Edit only the current roadmap slice and its tests. Do not perform unrelated cleanup.
- Stay within a maximum of 25 tool rounds.
- Run the narrowest relevant check first, then wider checks:
pnpm test(ornpm test),pnpm lint,pnpm build;cargo fmt --check --manifest-path src-tauri/Cargo.toml;cargo test --manifest-path src-tauri/Cargo.toml.
- Let command results determine success. Do not predict test outcomes.
- Reuse existing ALTAI runtime, event, state, and component patterns.
- Preserve unrelated working-tree changes.
- After two unsuccessful fixes for the same failure, stop and report evidence.
- Finish with: changed files, checks run, remaining risks, and the next roadmap item. Do not start the next item.
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.
- 5d ago First seen · 34 lines · 27 tokens per session scan A 374949004114
altai-implementer is an agent published in the GitHub repository altaidevorg/altai-app (2 stars, last pushed today), licensed Apache-2.0. It adds 27 tokens to every session and 301 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
PROJECT_MAP
Agent "PROJECT_MAP" from zyqzyq/Unfour, covering projectmap.md, top-level directory structure, frontend packages, @unfour/ui (packages/ui) and @unfour/command-client (packages/command-client).
EXECUTION_PROTOCOL
Default execution workflow for AI coding agents working on implementation or documentation tasks in this repository.
CHECKPOINT_REFRESH
Use this procedure to refresh repository progress documents after several completed task batches or after significant cross-layer changes.
START_HERE
This is the stable repository onboarding entrypoint for AI coding tools working in Unfour. Use it to choose the smallest useful context set before touching files.
PROJECT_STATE
The application is technically stable: all automated tests pass (98 Rust, 60 frontend), the production build succeeds, Windows keychain is runtime-verified, and browser UI smoke passes. However, the app is not ready for early basic release because live SSH server verification — the core use case for the Terminal…
NEXT_STEPS
Agent "NEXT_STEPS" from zyqzyq/Unfour, covering next steps, recommended: release gate and preparation and completed.