What is repo-decisions?

A set of instructions for maintaining MADR decision records, which are documents that explain important technical choices and the alternatives considered. It stores these records in a project’s `docs/decisions/` directory.

Use it when choosing between meaningful architectural or process alternatives, creating a new decision record, or updating or reviewing an existing one.

It preserves the reasoning behind choices that future maintainers may need to revisit, instead of leaving only the final code without context.

repo-decisions — Skill for Claude Code and Codex by EricSanchezok

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 EricSanchezok/repo-seed --skill repo-decisions

Clone the repo

git clone --depth 1 https://github.com/EricSanchezok/repo-seed

Made for: Claude Code, 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ericsanchezok/repo-seed/repo-decisions/github.svg)](https://agentmods.dev/skills/ericsanchezok/repo-seed/repo-decisions)

Your own site

<a href="https://agentmods.dev/skills/ericsanchezok/repo-seed/repo-decisions"><img src="https://agentmods.dev/badge/skills/ericsanchezok/repo-seed/repo-decisions/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ericsanchezok/repo-seed/repo-decisions"><img src="https://agentmods.dev/badge/skills/ericsanchezok/repo-seed/repo-decisions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 714 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.

Model	Per session	Once invoked
Fable 5.1	$0.00034	$0.00714
Opus 5	$0.00017	$0.00357
Sonnet 5	$0.00007	$0.00143
Haiku 4.5	$0.00003	$0.00071

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

Security

Grade A, and why

repo-decisions 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 12d 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.

.agents/skills/repo-decisions/SKILL.md · 47 lines

How it starts

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

Writing and updating decision records

The decision log in docs/decisions/ is the durable home for architecture and process choices with genuine alternatives. Its directory entry defines the local or external standard; this skill carries the procedure.

When a decision record is required

Write or update a decision record when a change chooses among meaningful alternatives and future maintainers may reasonably revisit the rationale. Do not create an ADR for routine implementation, a mechanical refactor, an obvious fix already defined by a regression test, or work that merely follows an accepted decision. Risk-boundary feature behavior belongs in a spec; commits retain change history.

Procedure: create a new record

Find the next sequential number in docs/decisions/ and take max + 1, zero-padded to 4 digits. Numbers are sequential starting at 0 and never change.
Create docs/decisions/NNNN-kebab-case-title.md.
Write the required sections in order:
- ## Status — first line is the status value; optional Class: <value> on the next line.
- ## Context and Problem Statement
- ## Decision Drivers
- ## Considered Options
- ## Decision Outcome
- ## Pros and Cons of the Options
- ## Links
State the decision, what it beats, and what it gives up. ## Considered Options lists genuine alternatives; ## Pros and Cons of the Options records why the losers lost. When the record relies on external evidence or an implementation source, cite it descriptively with a stable URL, DOI, or versioned permalink in ## Links; do not leave research or quantitative claims unlinked.
Cross-reference records with relative Markdown links ([0001](0001-title.md)), never bare numbers.
Run node scripts/verify-decisions.mjs.

Procedure: update an existing record

Status change to Accepted: the decision shipped. Keep the record current with what actually shipped (facts only — names, paths, structure — not the decision itself). Present tense.
Superseding: never rewrite an old record into its opposite. Create a new record, mark the old one Superseded by [NNNN](NNNN-title.md), and cross-link both.
Deprecation: a record that is no longer recommended but has no single successor becomes Deprecated.
Rejected: a proposal considered and declined. Keep it while its rationale prevents a tempting mistake; otherwise delete it.

Read the full file on GitHub · 47 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.

12d ago First seen · 47 lines · 34 tokens per session scan A b871e064a473

Subscribe to this mod's changes

repo-decisions is a skill published in the GitHub repository EricSanchezok/repo-seed (8 stars, last pushed 16d ago), licensed MIT. It adds 34 tokens to every session and 714 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-31.

Claude Code Planning Writing and docs agent-native agent-skills ai-agents codex cursor

blog-cms

Sets up and integrates OpenBlog — a Git-based blog CMS module for product sites (Markdown, Next.js, theme, chrome, sitemap/RSS). Routes agents to integrate on an existing site or scaffold greenfield. Use when the user mentions blog CMS, OpenBlog, /blog on a product site, headless blog, Git-backed blog, or…

kostja94/openblog · 78 tokens

integrate-product-site

Mount OpenBlog on an existing product website — chrome, deploy patterns, brand import. PRIMARY path. Use when the user already has a main site and wants /blog or blog subdomain. Ask the user to confirm before suggesting create-openblog.

kostja94/openblog · 54 tokens

setup-blog-module

Greenfield OpenBlog setup — scaffold, config, deploy env, theme, features, validate/build. Use when starting from scratch or user wants to try OpenBlog locally first. NOT the default if user has an existing product site — use integrate-product-site instead.

kostja94/openblog · 56 tokens

repo-decisions