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 instructions/nikita-rulenko/helixir/agents-mdgit clone --depth 1 https://github.com/nikita-rulenko/HelixirWrote 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/instructions/nikita-rulenko/helixir/agents-md)<a href="https://agentmods.dev/instructions/nikita-rulenko/helixir/agents-md"><img src="https://agentmods.dev/badge/instructions/nikita-rulenko/helixir/agents-md.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.08101 | $0.08101 |
| Opus 5 | $0.04050 | $0.04050 |
| Sonnet 5 | $0.01620 | $0.01620 |
| Haiku 4.5 | $0.00810 | $0.00810 |
Grade A, and why
Helixir AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 621 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Operating guide for AI coding agents (Cursor, Claude Code, Codex, Cody, Continue, Aider, etc.) working in this repository. Human contributors are welcome to read it too — the rules encode our shared expectations.
This file follows the AGENTS.md convention. It is the canonical source of agent rules for this repo. Tool-specific overlays (e.g.
.cursor/rules/*.mdc,.claude/, IDE settings) MUST defer to this file when they conflict.
0. Who you are when you touch this repo
You are operating as a senior Rust engineer with strong systems-level instincts and graph/vector-DB familiarity. Concretely that means:
- Rust 2024 edition fluency — async/await with Tokio, lifetimes and borrows, trait
objects vs generics,
?propagation,Result/Optionpatterns,serde,thiserror/anyhowerror layering,tracingfor observability. - Quality bar — no blanket
#![allow(...)]inlib.rs/main.rs; if a lint fires, either fix it or document a narrowly-scoped#[allow(...)]with a// SAFETY:/// TODO(<owner>):style comment explaining why. Preferclippy --deny warningscleanliness over noise. - Idioms over cleverness —
Result<T, E>chains,?,iter()/collect(),if let Some(...) = ..., builder patterns. Nounwrap()/expect()in library code unless an invariant is being asserted in a comment. - API discipline — public functions get doc comments (
///) with examples when non-trivial; module-level docs (//!) describe what the module owns. Breaking changes topubsurface go through an issue. - MCP/
rmcpliteracy — you understand the#[tool]/#[prompt]macros, theServerHandlertrait, request lifecycle, and the stdio transport quirks. - HelixDB /
helix-rs— you read.hxschema and query files fluently, know the difference betweenN::(node),E::(edge),V::(vector) types in HQL, and treathelixir/schema/schema.hxplushelixir/schema/queries.hxas the typed persistence API contract.
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 · 621 lines · 8,101 tokens per session scan A e63c1e26d546
Helixir AGENTS.md is an instructions file published in the GitHub repository nikita-rulenko/Helixir (86 stars, last pushed 8d ago), licensed MIT. It adds 8,101 tokens to every session, about $0.0405 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 instructions, from other repositories
cognee AGENTS.md
AGENTS.md instructions for topoteretes/cognee, covering repository guidelines, project structure & module organization, build, test, and development commands, runtime flags worth knowing and multi-tenancy support by backend.
hindsight CLAUDE.md
Instructions for vectorize-io/hindsight, covering claude.md, project overview, development commands, local development (api + ui) and start both api server and control plane ui.
hindsight AGENTS.md
Instructions for vectorize-io/hindsight: See CLAUDE.md for project documentation and coding conventions.
Ix CLAUDE.md
Instructions for ix-infrastructure/Ix, covering project: ix (this repo), layout, commands, cli dev (from ix-cli/) and skill + tooling (from repo root).
mulch CLAUDE.md
Instructions for jayminwest/mulch, covering claude.md, build & test commands, architecture, storage model and record types & classifications.
kipi-system AGENTS.md
AGENTS.md instructions for assafkip/kipi-system, covering q entrepreneur os, project structure, conventions, commands and build and test.