micropython-stubs: Instructions file for Codex

AGENTS.md

micropython-stubs AGENTS.md is an instructions file for Codex, OpenCode from Josverl/micropython-stubs. It costs 1,732 tokens per session, scanned C, a copy of awesome-spain AGENTS.md, MIT.

Repository instructions for the `micropython-stubs` project. They explain how the project uses Beads for task tracking, how its local task database syncs through Git, and how to run shell commands without unwanted prompts.

In plain words
What is it for?
Use them when working on `micropython-stubs`, especially for Beads issues, task synchronization, and non-interactive file commands.
Why use it?
They give coding agents project-specific rules so task data is not edited or synced through the wrong mechanism and file operations do not hang.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: names the TodoWrite tool; mentions Codex.

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

Reuse

Borrowing it

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

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 micropython-stubs AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/josverl/micropython-stubs/agents-md"><img src="https://agentmods.dev/badge/instructions/josverl/micropython-stubs/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,732 This file is loaded in full into every session.
When invoked 1,732 The same file — it is already loaded in full.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 80% copy Near-identical to another mod 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.01732 $0.01732
Opus 5.5 $0.00693 $0.00693
Sonnet 5.5 $0.00346 $0.00346
Haiku 4.5 $0.00173 $0.00173

Measured 18d ago against content hash 9ce7bb9d43d8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

micropython-stubs AGENTS.md scanned grade C with 1 finding 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 18d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf directory # NOT: rm -r directory
Origin

This is a copy

80% identical to awesome-spain AGENTS.md — 60 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 158 lines

How it starts

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

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd prime for full workflow context.

Architecture in one line: Issues live in a local Dolt database (.beads/dolt/); cross-machine sync uses bd dolt push/pull (a git-compatible protocol), stored under refs/dolt/data on your git remote — separate from refs/heads/* where your code lives. .beads/issues.jsonl is a passive export, not the wire protocol.

See sync-concepts for the one-screen overview and anti-patterns (don't treat JSONL as the source of truth; don't bd import during normal operation; don't reach for third-party Dolt hosting before trying the default).

Repository Beads Sync Policy

This repository explicitly authorizes agents to synchronize Beads-only Dolt history with the configured remote. This authorization does not include source Git commits, git pull, or git push.

At the start of every agent session, run these commands in order:

bd prime
bd hooks install
bd hooks list
bd dolt pull

bd hooks install is intentionally unconditional: it is idempotent and preserves unrelated hook content. Do not assume that hooks in a cloned repository are already active; confirm the installation with bd hooks list.

  • Run bd dolt pull before relying on issue status or mutating Beads.
  • Search for an existing issue before creating a replacement. Continue the original issue when possible; use bd supersede <old> --with <new> when a duplicate already exists.
  • After any successful Beads mutation, run bd dolt push before handoff.
  • Never use bd dolt push --force. If pull, merge, or push reports a conflict or failure, stop and report the exact error; do not claim the state is synced.
  • Git branch merges and rebases do not synchronize Beads. Beads state travels only through the Dolt remote at refs/dolt/data.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work atomically
bd close <id>         # Complete work
bd dolt push          # Push beads data to remote

Read the full file on GitHub · 158 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. 18d ago Changed · +29 lines · +278 tokens per session 9ce7bb9d43d8
  2. 20d ago First seen · 129 lines · 1,454 tokens per session scan C 548a8c678abd

Subscribe to this mod's changes

micropython-stubs AGENTS.md is an instructions file published in the GitHub repository Josverl/micropython-stubs (321 stars, last pushed yesterday), licensed MIT. It adds 1,732 tokens to every session, about $0.0069 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). It is 80% identical to awesome-spain AGENTS.md, differing in 60 lines, and is treated as a copy.

Related

Other instructions, from other repositories

agent-compass pr-workflow.instructions.md

Instructions for me-cedric/agent-compass: For PR creation, default base branch is develop. Assign the PR to yourself with --assignee @me. If reviewers are not specified, ask for at least one and list likely repo contributors. Use only labels that exist in gh label list.

me-cedric/agent-compass · 96 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 · 9,649 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,257 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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens