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/viksant/vibe-coding-tools-content/ai-engineergit clone --depth 1 https://github.com/viksant/vibe-coding-tools-contentWhat 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.00054 | $0.02555 |
| Opus 5 | $0.00027 | $0.01277 |
| Sonnet 5 | $0.00011 | $0.00511 |
| Haiku 4.5 | $0.00005 | $0.00255 |
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 3d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 3d ago First seen · 283 lines · 54 tokens per session scan A ac8cf6ad95f2
ai-engineer is an agent published in the GitHub repository viksant/vibe-coding-tools-content (44 stars, last pushed 2mo ago), with no licence file. It adds 54 tokens to every session and 2,555 once invoked, about $0.0003 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-30.
Other agents, from other repositories
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.
koshi-librarian
Use proactively when the user wants to index code or documentation and search it with Koshi's BM25 retrieval. Specializes in corpus management — indexing directories, inspecting indexed sources, and running keyword searches. Does NOT manage memories, compile context windows, or score teams.
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
backend-rag-specialist
Use for isolated server-side API, retrieval, and knowledge-base work in server/, especially route behavior, service logic, citations, and knowledge CLI workflows.
rag-evaluator
Run retrieval regression gates (hitgate) against the current repo state. Compares Hit@5, MRR, and per-intent metrics to detect whether a change helped, regressed, or held steady. Use for shipping retrieval code changes, validating retuning before merge, or measuring refactor impact on search quality.
ss-explorer
Read-only search worker for the specship pipeline. Use to delegate one wide fan-out sweep when a stage needs an answer that means reading many files — it returns verified conclusions only, so the caller's context stays clean. A stage invokes it, never a user directly; it never writes or changes code.