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/CronusL-1141/AI-companyWrote 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/cronusl-1141/ai-company/engineering-ai-engineer)<a href="https://agentmods.dev/agents/cronusl-1141/ai-company/engineering-ai-engineer"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/engineering-ai-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/cronusl-1141/ai-company/engineering-ai-engineer"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/engineering-ai-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.00040 | $0.00286 |
| Opus 5.5 | $0.00016 | $0.00114 |
| Sonnet 5.5 | $0.00008 | $0.00057 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
ai-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 24d 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
你是 AI/ML 工程师，负责模型集成、提示工程、检索与 Agent 工作流。
- Prompt 变更记下版本号与变更原因，效果回退时才找得到是哪一版引入的。
- 审查由派工方另行安排，不必自己再派审查者复核产出。超出任务范围的发现写进汇报的后续项，不顺手改：顺手的改动落在派工方的审查范围之外。
本仓库（AI Team OS）
- 记忆检索走 BM25（
src/aiteam/memory/retriever.py），没有 embedding、没有向量库。这是刻意选型不是缺口，要改检索方案先在报告里论证，别直接引入 pgvector/Milvus 一类依赖。 langchain系只在src/aiteam/orchestrator/作可选依赖懒加载，未安装是常态，别当既有基建用。
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.
- 24d ago Changed · +2 lines · -1 tokens per session f00e8d1425a8
- 1mo ago Changed · -159 lines 38910438a18b
- 1mo ago First seen · 175 lines · 41 tokens per session scan A 10de5b81cdc5
ai-engineer is an agent published in the GitHub repository CronusL-1141/AI-company (373 stars, last pushed 13d ago), licensed MIT. It adds 40 tokens to every session and 286 once invoked, about $0.0002 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-30.
Other agents, from other repositories
cortex
Designs and ships production AI features — LLM integration, prompt engineering, RAG pipelines, evals, and MLOps. Use when you need an AI architecture decision, a prompt-first vs RAG vs fine-tune call, or an eval harness for an existing feature. Trigger with "build this AI feature", "design the RAG pipeline".
ai-engineer
Build LLM applications, RAG systems, and prompt pipelines. Implements vector search, agent orchestration, and AI API integrations. Use PROACTIVELY for LLM features, chatbots, or AI-powered applications.
token
Optimizes LLM context windows through token budgeting, chunking strategy, and truncation design. Use when you need to control token spend, design a chunking pipeline, or audit token usage in a production AI system. Trigger with "design my token budget", "fix my context overflow".
prompt_engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…
research-assistant
Intelligent research agent that uses Agent Brain for knowledge retrieval with adaptive search modes.
ai-engineer
Build LLM applications, RAG systems, and prompt pipelines. Implements vector search, agent orchestration, and AI API integrations. Use PROACTIVELY for LLM features, chatbots, or AI-powered applications.