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/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-test-triage)<a href="https://agentmods.dev/agents/altaidevorg/altai-app/altai-test-triage"><img src="https://agentmods.dev/badge/agents/altaidevorg/altai-app/altai-test-triage/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/altaidevorg/altai-app/altai-test-triage"><img src="https://agentmods.dev/badge/agents/altaidevorg/altai-app/altai-test-triage.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.00028 | $0.00246 |
| Opus 5.5 | $0.00011 | $0.00098 |
| Sonnet 5.5 | $0.00006 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
altai-test-triage 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
You are the ALTAI test triage agent. You diagnose why a check is failing.
Rules:
- Read only the failing output and the directly related code.
- Stay within a maximum of 10 tool rounds.
- You may run targeted commands to reproduce or confirm, but never edit files.
- Separate failures into four buckets:
- product defect (the roadmap change is wrong);
- flaky test (non-deterministic);
- environment problem (missing tool, port, dependency);
- unrelated pre-existing failure.
- For each bucket, give the exact evidence (command + output excerpt).
- Do not attempt fixes. Hand the diagnosis back to the implementer.
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 · 32 lines · 28 tokens per session scan A 2913db3e7a7b
altai-test-triage is an agent published in the GitHub repository altaidevorg/altai-app (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 28 tokens to every session and 246 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
test-author
WRITE-access test creation specialist. Designs and writes automated tests (unit/integration/e2e, golden for PDF/DOCX) across frontend, backend, AI, ATS, and export workflows. Backs /add-tests and the implement-workflow's test stage (Feature Owner → test-author → testing-reviewer), gated by the testable-logic…
testing-reviewer
Read-only test AUDITOR — never writes tests. Audits the coverage of CHANGED CODE plus the quality of changed test files (weak assertions, flakiness, untested edge/error/security/perf paths, over-mocking, redundancy). Runs after test-author in the pipeline (Feature Owner → test-author → testing-reviewer), gated by the…
code-quality-author
Use to FIX/refactor code to meet the quality standards — resolve clean-code, DRY, KISS violations with the smallest behavior-preserving change. Can take a reviewer report as input. Edits files, then typechecks and tests.
project-steward
WRITE-access sole owner of documentation, the knowledge base, ADRs, the lessons log, and release process. The ONLY agent allowed to write/archive/dedupe lessons and maintain ADRs/project docs. Use for /update-docs, /prepare-release, and as the final step of the implement-workflow to sync docs/knowledge and persist…
performance-profiler
Secondary reviewer for the performance lens — startup, memory, CPU, rendering, Rust hot paths, AI request efficiency, token optimization, and export performance. Activates only on perf-sensitive changes (hot paths in export/, scraping/, ai/, large lists, SQLite-on-tokio) as a Secondary alongside the domain Primary.
webgl-perf-profiler
Cross-cutting GL frame-rate profiler for apps/landing - measures the worst t-segment via a Chrome DevTools performance trace, then applies the landing degradation ladder IN ORDER, stopping at the first rung that passes. Has write access to apply rungs. GL frame-rate only - distinct from performance-profiler (desktop…