zotero-comfort: Instructions file for Codex

AGENTS.md

zotero-comfort AGENTS.md is an instructions file for Codex, OpenCode from BIH-CEI/zotero-comfort. It costs 333 tokens per session, scanned A, a copy of awesome-spain AGENTS.md, MIT.

Project instructions for working on the Zotero Comfort codebase. They describe using Beads, an issue-tracking system, and require tests or other quality checks, synchronization, commits, and a successful push to the remote Git repository before work is considered complete.

In plain words
What is it for?
Use them when taking issues, updating their status, running checks after code changes, syncing with Git, pushing completed work, and preparing a session handoff.
Why use it?
They give coding agents a clear checklist for tracking work and handing it off without leaving changes or unfinished tasks only on a local machine.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 zotero-comfort AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bih-cei/zotero-comfort/agents-md"><img src="https://agentmods.dev/badge/instructions/bih-cei/zotero-comfort/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 333 This file is loaded in full into every session.
When invoked 333 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 59% 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.00333 $0.00333
Opus 5.5 $0.00133 $0.00133
Sonnet 5.5 $0.00067 $0.00067
Haiku 4.5 $0.00033 $0.00033

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

Security

Grade A, and why

zotero-comfort 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.

Origin

This is a copy

59% identical to awesome-spain AGENTS.md — 103 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 · 41 lines

What it actually says

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd onboard to get started.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git

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
    bd sync
    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 · 333 tokens per session scan A bf83e48f5820

Subscribe to this mod's changes

zotero-comfort AGENTS.md is an instructions file published in the GitHub repository BIH-CEI/zotero-comfort (1 stars, last pushed 5mo ago), licensed MIT. It adds 333 tokens to every session, about $0.0013 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 59% identical to awesome-spain AGENTS.md, differing in 103 lines, and is treated as a copy.

Related

zotero-comfort AGENTS.md compared with instructions from other repositories

zotero-comfort AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
zotero-comfort AGENTS.mdBIH-CEI/zotero-comfortInstructions file15mo agoMITA333Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode