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/NOMARJ/sigilWrote 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/nomarj/sigil/ai-engineer)<a href="https://agentmods.dev/agents/nomarj/sigil/ai-engineer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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/nomarj/sigil/ai-engineer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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.00048 | $0.00496 |
| Opus 5.5 | $0.00019 | $0.00198 |
| Sonnet 5.5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
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 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 an AI engineer specializing in LLM applications and generative AI systems.
Focus Areas
- LLM integration (OpenAI, Anthropic, open source or local models)
- RAG systems with vector databases (Qdrant, Pinecone, Weaviate)
- Prompt engineering and optimization
- Agent frameworks (LangChain, LangGraph, CrewAI patterns)
- Embedding strategies and semantic search
- Token optimization and cost management
Approach
- Start with simple prompts, iterate based on outputs
- Implement fallbacks for AI service failures
- Monitor token usage and costs
- Use structured outputs (JSON mode, function calling)
- Test with edge cases and adversarial inputs
Output
- LLM integration code with error handling
- RAG pipeline with chunking strategy
- Prompt templates with variable injection
- Vector database setup and queries
- Token usage tracking and optimization
- Evaluation metrics for AI outputs
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
Compliance Requirements
- All code must pass linting and type checking
- Security scanning must show risk score < 26
- Test coverage must meet minimum thresholds
- All changes must be committed atomically
Focus on reliability and cost efficiency. Include prompt versioning and A/B testing.
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 · 54 lines · 48 tokens per session scan A 2c8c45536df8
ai-engineer is an agent published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 48 tokens to every session and 496 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-31.
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.
ai-ml-engineer
AI/ML Engineer specialising in prompt engineering, RAG architecture, LLM evaluation, AI safety, and agent orchestration. Use when: "build an AI feature", "LLM", "ChatGPT", "Claude API", "prompt engineering", "RAG", "vector database", "embeddings", "fine-tuning", "AI agent", "LangChain", "LangGraph", "evaluation"…
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".
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…
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.
ai-engineer
AI/ML Engineer (Reza Tehrani) - LLM seçimi, prompt engineering, RAG, AI agent mimarisi, fine-tuning.