filesystem-context-discipline

filesystem-context-discipline is a skill for Codex from markoblogo/abvx-agent-skills. It costs 49 tokens per session (551 once invoked), scanned A, original, MIT.

A method for storing plans, evidence, scratch notes, handoffs, and other working context in organized files.

In plain words
What is it for?
Use it to retain generated proposals, track validation results, share handoffs between agents, and keep durable project guidance discoverable.
Why use it?
It keeps important context available across long tasks or sessions without filling the active conversation with every detail.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions AGENTS.md.

Good fit Use it to retain generated proposals, track validation results, share handoffs between agents, and keep durable project guidance discoverable.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/markoblogo/abvx-agent-skills/filesystem-context-discipline
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.

Any agent
npx skills add markoblogo/abvx-agent-skills --skill filesystem-context-discipline
Clone the repo
git clone --depth 1 https://github.com/markoblogo/abvx-agent-skills

Made for: Codex.

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 filesystem-context-discipline

README.md
[![agentmods](https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/filesystem-context-discipline/github.svg)](https://agentmods.dev/skills/markoblogo/abvx-agent-skills/filesystem-context-discipline)
Your own site
<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/filesystem-context-discipline"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/filesystem-context-discipline/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 filesystem-context-discipline

Your own site · 80×15
<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/filesystem-context-discipline"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/filesystem-context-discipline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 551 The whole file, excluding the scripts and references it only reads on demand.
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.00049 $0.00551
Opus 5 $0.00024 $0.00275
Sonnet 5 $0.00010 $0.00110
Haiku 4.5 $0.00005 $0.00055

Measured 10d ago against content hash 62e9983d91d4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

filesystem-context-discipline 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 10d 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.

skills/filesystem-context-discipline/SKILL.md · 66 lines

How it starts

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

Filesystem Context Discipline

Use the filesystem to hold durable state, but keep it structured, discoverable, and reviewable.

Use When

  • a task is too long for one prompt or needs resumable state;
  • generated output should be retained before apply;
  • a plan, checklist, evidence ledger, or handoff must survive compaction;
  • multiple agents or sessions need a shared artifact;
  • repo-local context should be discoverable without always loading it.

Context Types

  • scratchpad: temporary reasoning support, not authoritative.
  • plan: current intended steps, assumptions, and done criteria.
  • evidence: commands, test results, source links, or reviewed facts.
  • retained_output: proposal artifacts kept separate from the target workspace.
  • handoff: compact continuation state for another session or agent.
  • durable_doc: stable repo guidance that future agents should read on demand.

Workflow

  1. Choose the file type before writing.
  2. Put the artifact in the narrowest sensible location:
    • repo docs for durable guidance;
    • task/proposal folder for retained output;
    • benchmark or run folder for validation evidence;
    • memory only when the user explicitly asks to preserve a cross-session lesson.
  3. Add enough metadata for later discovery: task, source, status, owner, date, and apply state when relevant.
  4. Keep scratchpads separate from durable docs.
  5. Link retained outputs to their inspection and settlement decision.
  6. Remove or ignore transient files before commit unless they are intentional artifacts.

Output Shape

Use:

  • artifact type;
  • path;
  • authority level: scratch, proposal, evidence, or durable;
  • discovery cue;
  • expiry or update trigger;
  • related verification or settlement step.

Guardrails

  • Do not make every thought durable.
  • Do not mix speculative scratchpad text into README, AGENTS.md, or SKILL.md.
  • Do not treat retained output as applied work.
  • Do not use hidden files as the only record of an important decision.
  • Do not write memory unless the user explicitly asked for memory persistence.

Read the full file on GitHub · 66 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 66 lines · 49 tokens per session scan A 62e9983d91d4

Subscribe to this mod's changes

filesystem-context-discipline is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 551 once invoked, about $0.0002 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-30.