awesome-spain: Instructions file for Codex

AGENTS.md

awesome-spain AGENTS.md is an instructions file for Codex, OpenCode from GeiserX/awesome-spain. It costs 1,203 tokens per session, scanned C, original, CC0-1.0.

Repository instructions for the `awesome-spain` project, covering its Beads issue-tracking workflow, commands, data storage, synchronization, and shell-operation rules. Beads stores issues in a local database and synchronizes them separately from ordinary code branches.

In plain words
What is it for?
Use them when working on the `awesome-spain` repository, especially for finding, claiming, closing, and synchronizing Beads issues.
Why use it?
They give a coding agent project-specific rules so it uses the intended issue workflow and avoids treating exported data as the source of truth.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 awesome-spain AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/geiserx/awesome-spain/agents-md"><img src="https://agentmods.dev/badge/instructions/geiserx/awesome-spain/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,203 This file is loaded in full into every session.
When invoked 1,203 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 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.01203 $0.01203
Opus 5.5 $0.00481 $0.00481
Sonnet 5.5 $0.00241 $0.00241
Haiku 4.5 $0.00120 $0.00120

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

Security

Grade C, and why

awesome-spain 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 11d 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

Copies of this mod

8 near-identical copies found in the catalogue:

AGENTS.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 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.md 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).

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

Non-Interactive Shell Commands

ALWAYS use non-interactive flags with file operations to avoid hanging on confirmation prompts.

Shell commands like cp, mv, and rm may be aliased to include -i (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.

Use these forms instead:

# Force overwrite without prompting
cp -f source dest           # NOT: cp source dest
mv -f source dest           # NOT: mv source dest
rm -f file                  # NOT: rm file

# For recursive operations
rm -rf directory            # NOT: rm -r directory
cp -rf source dest          # NOT: cp -r source dest

Other commands that may prompt:

  • scp - use -o BatchMode=yes for non-interactive
  • ssh - use -o BatchMode=yes to fail instead of prompting
  • apt-get - use -y flag
  • brew - use HOMEBREW_NO_AUTO_UPDATE=1 env var

Beads Issue Tracker

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

Read the full file on GitHub · 108 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. 11d ago Changed · -19 tokens per session 55c0c729aaec
  2. 13d ago First seen · 108 lines · 1,222 tokens per session scan C c0d36a6db66a

Subscribe to this mod's changes

awesome-spain AGENTS.md is an instructions file published in the GitHub repository GeiserX/awesome-spain (357 stars, last pushed 3d ago), licensed CC0-1.0. It adds 1,203 tokens to every session, about $0.0048 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-03.

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

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