Borrowing it
Nothing to install: this file belongs to Foxfire1st/agents-remember. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Foxfire1st/agents-remember/main/.agents/skills/c-02-memory-quality-control/SKILL.mdgit clone --depth 1 https://github.com/Foxfire1st/agents-rememberWrote 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/foxfire1st/agents-remember/c-02-memory-quality-control)<a href="https://agentmods.dev/skills/foxfire1st/agents-remember/c-02-memory-quality-control"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-02-memory-quality-control.svg" alt="Measured on agentmods" 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.00034 | $0.02572 |
| Opus 5 | $0.00017 | $0.01286 |
| Sonnet 5 | $0.00007 | $0.00514 |
| Haiku 4.5 | $0.00003 | $0.00257 |
Grade A, and why
c-02-memory-quality-control 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 7d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
c-02-memory-quality-control Memory Quality Control
Use this skill whenever a workflow needs to decide whether the memory layer is safe to rely on, whether newly added source files have onboarding pairs before a code commit, or whether memory is clean enough to commit during closeout.
The skill owns the memory quality control procedure. Drift detection remains the
task-start trust baseline, but it is now one integrity check inside the broader
memory_quality domain.
Inputs
This skill operates on one repository at a time and starts from the context
resolved by c-08-ar-coordination-context-resolver or MCP resolve_context.
Primary Outputs
- task-start trust guidance from repo-wide drift classification
- a concrete onboarding maintenance worklist for
c-05-create-or-update-onboarding-files - a pre-code-commit missing-onboarding report for newly added source files
- a closeout memory quality report covering integrity and style checks
- explicit next actions when memory quality is not clean
- one atomically overwritten curator checklist inside a leaf's worktree enclosure
Quality Control Phases
| Phase | Check | Purpose |
|---|---|---|
| Task start | drift_check |
Decide whether existing onboarding is trustworthy enough to plan against. |
| Curator intake and repair loop | contract-scoped memory_quality_check |
Replace one enclosure-local checklist combining quality, missing-onboarding, drift candidates, and route-index preview. |
| Before code commit | check_missing_onboarding |
Catch new source files in the current worktree that need sidecars before the code commit lands. |
| Before memory commit | memory_quality_check |
Validate refreshed memory after code commit and onboarding updates, including drift integrity and memory style. |
| Targeted style repair | history_order_fix.py |
Fix update-history ordering only after the report identifies that mechanical issue. |
Style checks are closeout quality control. They should not block the beginning of normal implementation work.
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.
- 7d ago First seen · 268 lines · 34 tokens per session scan A e5595d71a6c0
c-02-memory-quality-control is a skill published in the GitHub repository Foxfire1st/agents-remember (27 stars, last pushed 6d ago), licensed MIT. It adds 34 tokens to every session and 2,572 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.
Other skills, from other repositories
obsidian-memory
Cross-project long-term memory over an Obsidian brain vault: recall relevant notes before a task, and persist distilled conclusions (decisions, pitfalls, solutions, progress) back after a task. The vault is an optional aggregation/projection layer — repo-local artifacts stay the per-project source of truth, and sync…
memwal
Walrus Memory SDK — portable agent memory that works across apps, sessions, and workflows. Use when users say: "add memory to my app" "portable agent memory" "integrate Walrus Memory" "AI agent memory" "memory across agents" "Walrus memory storage" "setup Walrus Memory" "recall memories".
cortex-automate
Set up automation — prospective memory triggers, neuro-symbolic rules, and CLAUDE.md sync. Use when the user says 'remind me when', 'trigger when', 'create a rule', 'auto-remember', 'sync to CLAUDE.md', 'push insights', 'set up trigger', 'when I open this file', 'when this keyword appears', or when you want to…
cortex-profile
View and manage your cognitive profile — how you think, work patterns, blind spots, and cross-domain connections. Use when the user says 'show my profile', 'how do I work', 'what are my patterns', 'cognitive style', 'blind spots', 'methodology', or at the start of a session to load context. Also use 'rebuild profile'…
cortex-recall
Search and retrieve memories from Cortex persistent memory. Use when the user asks 'what did we decide about X', 'do you remember', 'what was the fix for', 'find that thing about', 'search memories', 'what do we know about', 'have we seen this before', or when you need context about past decisions, patterns, bugs, or…
cortex-remember-global
Store a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global…