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-01-findings-capture/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-01-findings-capture)<a href="https://agentmods.dev/skills/foxfire1st/agents-remember/c-01-findings-capture"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-01-findings-capture/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/foxfire1st/agents-remember/c-01-findings-capture"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-01-findings-capture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00450 |
| Opus 5 | $0.00017 | $0.00225 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
c-01-findings-capture 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.
How it starts
The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
c-01-findings-capture Findings Capture
Use this skill when durable knowledge emerges during developer discussion, task execution, review, or direct clarification and should not remain stranded in chat.
Companion file:
findings-capture-workflow.md
Operating Modes
- Inside a task workflow (an
l-01-agent-lifecyclesorchestrator build phase or aw-02-light-task-workflowtask, including a master + light sub-task series). - Standalone during direct clarification.
Durable Destinations
Route the finding to the owning durable surface:
requirement_change_candidates.mdwhen the finding changes scope, requirements, or developer intent.architecture_open_questions.mdwhen the finding exposes a structural decision, dependency boundary, or design uncertainty.- The active phase artifact when the finding is planning-, implementation-, or review-local and belongs to the current task flow.
- Onboarding through
c-05-create-or-update-onboarding-fileswhen the finding is a verified factual current-state clarification that should survive outside the task.
Rules
- Verify relevant code and onboarding before durable capture when possible.
- Do not copy developer clarifications into onboarding verbatim. Check them against code reality first; when code contradicts or only partially supports the clarification, surface the mismatch and resolve it before durable capture.
- Ask targeted follow-up questions if the finding is still ambiguous.
- Do not rewrite approved
requirements.mdorarchitecture.mddirectly from one finding without developer approval. - Do not send speculative, future-state, unresolved, or task-only notes into onboarding.
- If a finding affects both task-local artifacts and onboarding, update the task-local owner first, then propagate to onboarding only if the factual guardrail is satisfied.
- Use broader discovery only when direct code and onboarding checks are not enough.
- Never leave a confirmed finding only in chat when an appropriate durable destination exists.
What ships with it
1 file 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.
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.
- 10d ago First seen · 40 lines · 35 tokens per session scan A c6b5f4e02cc9
c-01-findings-capture is a skill published in the GitHub repository Foxfire1st/agents-remember (27 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 450 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-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…
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-consolidate
Run memory maintenance — decay old memories, compress stale content, consolidate episodic memories into semantic knowledge, and run sleep-like replay. Use when the user says 'clean up memories', 'consolidate', 'run maintenance', 'compress old memories', 'memory cleanup', or periodically to keep the memory system…
cortex-navigate-knowledge
Navigate the knowledge graph — trace entity relationships, explore causal chains, drill into memory clusters, and traverse co-access paths. Use when the user asks 'how are these related', 'what connects X to Y', 'show me the knowledge graph', 'trace the relationship', 'what caused X', 'drill down into', 'explore…