claudeconfigurator: Instructions file for Codex

AGENTS.md

claudeconfigurator AGENTS.md is an instructions file for Codex, OpenCode from tcsenpai/claudeconfigurator. It costs 2,488 tokens per session, scanned A, original, MIT.

Project instructions for using Mycelium, a task-management tool, to organize work in the claudeconfigurator repository. They cover epics, tasks, priorities, dependencies, assignments, and exports.

In plain words
What is it for?
Use them to create and manage epics, assign tasks, link blocked work, connect GitHub issues or pull requests, and export project data.
Why use it?
They provide a consistent way to track large pieces of work and the smaller tasks that depend on them.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; positional $N argument.

This is tcsenpai/claudeconfigurator's own configuration. It tells Codex and OpenCode how to work on claudeconfigurator 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 claudeconfigurator configures →

Reuse

Borrowing it

Nothing to install: this file belongs to tcsenpai/claudeconfigurator. 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/tcsenpai/claudeconfigurator/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/tcsenpai/claudeconfigurator

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 claudeconfigurator AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tcsenpai/claudeconfigurator/agents-md.svg)](https://agentmods.dev/instructions/tcsenpai/claudeconfigurator/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/tcsenpai/claudeconfigurator/agents-md"><img src="https://agentmods.dev/badge/instructions/tcsenpai/claudeconfigurator/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,488 This file is loaded in full into every session.
When invoked 2,488 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.02488 $0.02488
Opus 5 $0.01244 $0.01244
Sonnet 5 $0.00498 $0.00498
Haiku 4.5 $0.00249 $0.00249

Measured 6d ago against content hash 4c2a91bf54ed, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

claudeconfigurator 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 6d 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 · 239 lines

How it starts

The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

Project Management with Mycelium

This project uses Mycelium (myc) for task and epic management.

Quick Reference

# Initialize mycelium in this project (creates .mycelium/ directory)
myc init

# Create an epic (a large body of work)
myc epic create --title "Feature X" --description "Build feature X"

# Create tasks within an epic
myc task create --title "Implement Y" --description "Build the implementation for Y" --epic 1 --priority high --due 2025-12-31

# Task priorities: low, medium, high, critical
# Task status: open, closed

# List tasks
myc task list
myc task list --epic 1
myc task list --overdue
myc task list --blocked

# Manage dependencies (task 1 blocks task 2)
myc task link blocks --task 1 2
myc deps show 2

# Close tasks (blocked tasks cannot be closed without --force)
myc task close 1

# Assign tasks
myc assignee create --name "Alice" --github "alice"
myc task assign 1 1

# Link to external resources
myc task link github-issue --task 1 "owner/repo#123"
myc task link github-pr --task 1 "owner/repo#456"
myc task link url --task 1 "https://example.com"

# Project overview
myc summary

# Export data
myc export json
myc export csv

Data Model

  • Epic: A large body of work with a title and optional description (e.g., a feature or milestone)
  • Task: A unit of work with a title and optional description, optionally linked to an epic
  • Dependency: Task A blocks Task B (B cannot close until A is closed)
  • Assignee: Person assigned to a task (can have GitHub username)
  • External Ref: Link to GitHub issues/PRs or URLs

Git Tracking

The .mycelium/ directory contains the SQLite database and should be committed to git:

git add .mycelium/
git commit -m "Add mycelium project tracking"

Follow-ups (myc followup, alias myc fu)

Lightweight scratch table for non-blocking "oh-by-the-way" items captured mid-work — bugs, questions, ideas, things the user should look at later. Separate from tasks (no epic/priority/deps/assignee). Most follow-ups are resolved by the user, not the agent.

Read the full file on GitHub · 239 lines

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. 6d ago First seen · 239 lines · 2,488 tokens per session scan A 4c2a91bf54ed

Subscribe to this mod's changes

claudeconfigurator AGENTS.md is an instructions file published in the GitHub repository tcsenpai/claudeconfigurator (10 stars, last pushed 1mo ago), licensed MIT. It adds 2,488 tokens to every session, about $0.0124 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-31.

Related

Other instructions, from other repositories

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,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

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 · 6,785 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens