record

A way to keep lasting architecture decisions, requirements, and system designs recorded and consistent across a codebase.

In plain words
What is it for?
Use it when establishing or changing long-term technical decisions, public interfaces, operational rules, or repository conventions.
Why use it?
It prevents important boundaries, contracts, ownership rules, and project-wide conventions from becoming outdated or being forgotten.

Skill for Claude CodeCodex

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 skills/kdlbs/kandev/record
Any agent
npx skills add kdlbs/kandev --skill record
Clone the repo
git clone --depth 1 https://github.com/kdlbs/kandev

Made for: Claude Code, Codex.

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 651 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00057 $0.00651
Opus 5 $0.00028 $0.00326
Sonnet 5 $0.00011 $0.00130
Haiku 4.5 $0.00006 $0.00065

Measured 3d ago against content hash 98afaf483b3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

record 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 3d 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/record/SKILL.md · 95 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 3d ago First seen · 95 lines · 57 tokens per session scan A 98afaf483b3c

Subscribe to this mod's changes

record is a skill published in the GitHub repository kdlbs/kandev (710 stars, last pushed 3d ago), licensed AGPL-3.0. It adds 57 tokens to every session and 651 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

process-builder

Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.

a5c-ai/babysitter · 32 tokens

retrospect-external-babysitter-run

For a repository in the babysitter-users catalog, locate its babysitter processes and any committed runs (.a5c/runs/ /) and perform a retrospective on a chosen run -- what went well, what failed, process suggestions, quality of effect design, breakpoint patterns -- mirroring the /babysitter:retrospect workflow but…

a5c-ai/babysitter · 120 tokens

pr-integration-test

Design, implement, and validate Intelligent Terminal integration tests for a target pull request or regression. Use when asked to add PR integration tests, convert a bug fix into E2E coverage, prove existing behavior still works, map tests to the release checklist, or verify E2E reports mark checklist cases complete.

microsoft/intelligent-terminal · 66 tokens

ultraapp-interview

Use when the user opens a Forge tab in the claw-orchestrator dashboard to start building a new ultraapp. Drives a structured Q&A interview that produces a complete AppSpec, then signals readiness to build.

Enderfga/claw-orchestrator · 48 tokens

test-driven-development

Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.

a5c-ai/babysitter · 35 tokens

product-brief-creation

Create comprehensive product briefs from market, domain, and technical research.

a5c-ai/babysitter · 0 tokens