helixir: Instructions file for Codex

AGENTS.md

helixir AGENTS.md is an instructions file for Codex, OpenCode from bookedsolidtech/helixir. It costs 345 tokens per session, scanned A, original, MIT.

Instructions for finishing work in Helixir, a project that tracks tasks with GitHub Issues, which are records for reporting and managing development work. They replace the retired Beads workflow.

In plain words
What is it for?
Listing, creating, viewing, and closing GitHub issues; running tests or linters; pulling, committing, pushing, and handing work to the next session.
Why use it?
They make completion include quality checks, issue updates, committed changes, and a successful push to the shared repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is bookedsolidtech/helixir's own configuration. It tells Codex and OpenCode how to work on helixir itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything helixir configures →

Reuse

Borrowing it

Nothing to install: this file belongs to bookedsolidtech/helixir. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/bookedsolidtech/helixir/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/bookedsolidtech/helixir

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for helixir AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bookedsolidtech/helixir/agents-md/github.svg)](https://agentmods.dev/instructions/bookedsolidtech/helixir/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/bookedsolidtech/helixir/agents-md"><img src="https://agentmods.dev/badge/instructions/bookedsolidtech/helixir/agents-md/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.

agentmods 80×15 button for helixir AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bookedsolidtech/helixir/agents-md"><img src="https://agentmods.dev/badge/instructions/bookedsolidtech/helixir/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 345 This file is loaded in full into every session.
When invoked 345 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00345 $0.00345
Opus 5.5 $0.00138 $0.00138
Sonnet 5.5 $0.00069 $0.00069
Haiku 4.5 $0.00034 $0.00034

Measured 2mo ago against content hash 656fd3a39380, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

AGENTS.md · 41 lines

What it actually says

Agent Instructions

This project tracks issues via GitHub Issues. The previous Beads (bd) workflow has been retired — .beads/ was removed in the rea-migration work and is no longer maintained.

Quick Reference

gh issue list                                # See open issues
gh issue view <number>                       # View issue details
gh issue create --title "..." --body "..."   # File new issue
gh issue close <number>                      # Close issue

Landing the Plane (Session Completion)

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

  1. File issues for remaining work - Create issues for anything that needs follow-up
  2. Run quality gates (if code changed) - Tests, linters, builds
  3. Update issue status - Close finished work, update in-progress items
  4. PUSH TO REMOTE - This is MANDATORY:
    git pull --rebase
    git push
    git status  # MUST show "up to date with origin"
    
  5. Clean up - Clear stashes, prune remote branches
  6. Verify - All changes committed AND pushed
  7. Hand off - Provide context for next session

CRITICAL RULES:

  • Work is NOT complete until git push succeeds
  • NEVER stop before pushing - that leaves work stranded locally
  • NEVER say "ready to push when you are" - YOU must push
  • If push fails, resolve and retry until it succeeds
Changes

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.

  1. 2mo ago First seen · 41 lines · 345 tokens per session scan A 656fd3a39380

Subscribe to this mod's changes

helixir AGENTS.md is an instructions file published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 4mo ago), licensed MIT. It adds 345 tokens to every session, about $0.0014 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens