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.
npx skills add ArcticFox2029/chamnan --skill remembergit clone --depth 1 https://github.com/ArcticFox2029/chamnanWrote 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.
[](https://agentmods.dev/skills/arcticfox2029/chamnan/remember)<a href="https://agentmods.dev/skills/arcticfox2029/chamnan/remember"><img src="https://agentmods.dev/badge/skills/arcticfox2029/chamnan/remember/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.
<a href="https://agentmods.dev/skills/arcticfox2029/chamnan/remember"><img src="https://agentmods.dev/badge/skills/arcticfox2029/chamnan/remember.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00040 | $0.01717 |
| Opus 5.5 | $0.00016 | $0.00687 |
| Sonnet 5.5 | $0.00008 | $0.00343 |
| Haiku 4.5 | $0.00004 | $0.00172 |
Grade A, and why
remember 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write down why
The code says what. The git history says when. Neither says why, and why is the expensive part to reconstruct — usually at the moment somebody is about to undo it.
When to write an entry
Write one when the answer to "why is it like this?" took real work to arrive at, and would take real work to arrive at again.
Good reasons to write:
- a choice was made between two viable options and the loser is not obvious from the code
- something was tried, failed, and the failure is not visible in the repository
- a constraint exists that a newcomer would break without knowing
Do not write an entry when:
- the code already says it — a well-named function does not need a memory entry
- the git history already says it — a good commit message is the right place for "what changed"
- it is a task, not knowledge — that is
STATE.mdor a session record - it is a procedure — that is
/chamnan:capture
This is not a conversation log. Never paste a transcript. Write the conclusion.
Pick a category
The three are used differently, which is why they are separate:
decisions/ |
A choice and its reasoning | "Postgres over SQLite — two writers, and SQLite's locking showed up under load." |
lessons/ |
Something that cost time once | "Editing src/ while the app runs throws an AttributeError. It is a hot-reload artifact, not a bug — restart clears it." |
rules/ |
A standing constraint | "Never add a Cloud fallback for embeddings — a different model means an incompatible vector space." |
Rules are injected into every session. Decisions and lessons contribute their title, and the
agent reads the file when the title looks relevant. So put a constraint in rules/ only if it
should be in front of the agent before it starts — otherwise it is a decision, and the difference
matters to what every session costs.
Where it goes
.chamnan/memory/<category>/<short-slug>.md
A short, specific filename: postgres-over-sqlite.md, not database.md. The filename is what
appears in the session listing beside the title, so it should be recognisable on its own.
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.
- 1mo ago Changed · +17 lines 6f9ea2c94397
- 1mo ago Changed · +7 lines 286b45c823a6
- 1mo ago Changed · +10 lines 3c3e13111895
- 1mo ago First seen · 117 lines · 40 tokens per session scan A 997c8ba14524
remember is a skill published in the GitHub repository ArcticFox2029/chamnan (10 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 1,717 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
code-review
Code review practices with technical rigor and verification gates. Use for receiving feedback, requesting code-reviewer subagent reviews, or preventing false completion claims in pull requests.
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
cloudflare-cron-triggers
Cloudflare Cron Triggers for scheduled Workers execution. Use for periodic tasks, scheduled jobs, or encountering handler not found, invalid cron expression, timezone errors.
cloudflare-durable-objects
Cloudflare Durable Objects for stateful coordination and real-time apps. Use for chat, multiplayer games, WebSocket hibernation, or encountering class export, migration, alarm errors.
cloudflare-nextjs
Deploy Next.js to Cloudflare Workers via the OpenNext adapter (@opennextjs/cloudflare). Use for SSR/ISR/SSG/App or Pages Router, getCloudflareContext, bindings (D1/R2/KV/AI/Hyperdrive), caching tiers, skew protection, multi-worker, custom worker, env vars, or worker…
cloudflare-workers-testing
Comprehensive testing guide for Cloudflare Workers using Vitest and @cloudflare/vitest-pool-workers. Use for test setup, binding mocks (D1/KV/R2/DO), integration tests, or encountering test failures, mock errors, coverage issues.