agentmods.dev

workfile AGENTS.md

Project instructions for Workfile, a tool that stores searchable project context and tracks work items. They define required preparation, change tracking, review states, and verification steps.

In plain words
What is it for?
Use them when changing an illodev/workfile project: read the required protocol and workflow, search existing context, claim work cards, record discoveries, and run the project health check before finishing.
Why use it?
They give contributors a shared process for making changes and recording what remains to be done. This helps prevent undocumented work and treats completion as something that needs runtime evidence.

Instructions file for CodexOpenCode

2 5d ago A scan 175 tokens original MIT
View the source file illodev/workfile
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/illodev/workfile/agents-md
Clone the repo
git clone --depth 1 https://github.com/illodev/workfile

Made for: Codex, OpenCode.

Per session 175 This file is loaded in full into every session.
When invoked 175 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00175 $0.00175
Opus 5 $0.00088 $0.00088
Sonnet 5 $0.00035 $0.00035
Haiku 4.5 $0.00017 $0.00017

Measured yesterday against content hash e0c59de62112, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workfile 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 yesterday.

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

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 15 lines

What it actually says

Workfile for AGENTS.md

Before substantial changes, read .project/agents/protocol.md and the relevant workflow under .project/agents/workflows.

Critical rules:

  • Search context with pnpm workfile search or pnpm workfile agents context.
  • Claim cards before modifying their scope.
  • Use CLI/MCP for protocol mutations.
  • review means verification is pending; done requires runtime evidence.
  • Create cards for discovered pending work and record durable knowledge.
  • Run pnpm workfile doctor before finishing.
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. yesterday First seen · 15 lines · 175 tokens per session scan A e0c59de62112

Subscribe to this mod's changes

workfile AGENTS.md is an instructions file published in the GitHub repository illodev/workfile (2 stars, last pushed 5d ago), licensed MIT. It adds 175 tokens to every session, about $0.0009 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.

Code reviewGit and workflowProject managementagentsai-agentsbacklogchangelogclideveloper-tools
Related

Other instructions, from other repositories

agent-device AGENTS.md

AGENTS.md instructions for callstack/agent-device, covering agents.md, incident-derived principles, declaration sites and enforcement, hard repository rules and module and test topology.

callstack/agent-device · 2,120 tokens

beads AGENTS.md

AGENTS.md instructions for gastownhall/beads, covering agent instructions, key sections, project scope, pr safety for agents and visual design anti-patterns.

gastownhall/beads · 2,901 tokens

ai-agent-board AGENTS.md

Instructions for DanWahlin/ai-agent-board, covering agents.md, project overview, architecture, key technical decisions and running locally.

DanWahlin/ai-agent-board · 2,948 tokens

lineark CLAUDE.md

Instructions for flipbit03/lineark, covering claude.md — lineark, what is this, workspace layout, key commands and writing online tests: the three pillars.

flipbit03/lineark · 3,334 tokens

blz AGENTS.md

Instructions for outfitter-dev/blz, covering blz repository instructions for ai agents, important, working memory, use blz and 🚀 quick start for agents.

outfitter-dev/blz · 1,615 tokens

moo-tasks AGENTS.md

Instructions for dizlexic/moo-tasks, covering agents.md, 1. what is the moo tasks board?, 2. connecting your agent, 3. available mcp tools and 4. recommended workflow for agents.

dizlexic/moo-tasks · 3,550 tokens