Borrowing it
Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.agents/skills/sova-extract-knowledge/SKILL.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/sova-extract-knowledge)<a href="https://agentmods.dev/skills/xsovad06/sova/sova-extract-knowledge"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-extract-knowledge/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/xsovad06/sova/sova-extract-knowledge"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/sova-extract-knowledge.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.00019 | $0.01246 |
| Opus 5.5 | $0.00008 | $0.00498 |
| Sonnet 5.5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
sova-extract-knowledge 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 14d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract Knowledge
Review this session's work and extract reusable knowledge into the project's knowledge system.
Knowledge Architecture
This project uses a four-tier knowledge system:
Tier 0: ~/.claude/shared-knowledge/ (cross-project patterns)
Reusable patterns that apply across multiple repositories. Loaded by agent startup scripts.
Tier 1: .claude/rules/*.md (project rules, always loaded)
Stable patterns loaded into every session via CLAUDE.md. Primary destination for confirmed conventions that apply to all contributors (human and agent).
Tier 2: .claude/agent-memory/ (agent learnings)
Lessons learned from development and review cycles. Destination for agent-specific patterns not yet promoted to Tier 1.
MEMORY.md: index file (if the project has one)cookbook/<domain>.md(index incookbook/README.md), or a singlecookbook.mdin smaller projects: topical knowledge by domain, one bullet per lesson with(PR #N; confirmed: N)common-mistakes.md: recurring mistakes with(occurrences: N), checked against every diff by thesova-reviewskill
Always write Tier 2 files in the PRIMARY checkout (git rev-parse --git-common-dir resolves it from a worktree): .claude/agent-memory/ may be gitignored, and a worktree's copy is deleted with the worktree.
Tier 3: User auto-memory (~/.claude/projects/.../memory/)
User preferences, workflow conventions, and project state.
Steps
1. Identify What Changed
Run git diff and git diff --cached to see current changes. Also review the conversation for patterns, gotchas, decisions, and fixes that came up during the session.
2. Categorize Findings
For each finding, determine the right destination:
| Finding type | Destination |
|---|---|
| Domain-specific patterns (security, performance, etc.) | .claude/rules/<domain>.md |
| ORM/framework gotchas, review lessons | the matching .claude/agent-memory/cookbook/<domain>.md (or the section of cookbook.md) |
| Recurring mistakes | .claude/agent-memory/common-mistakes.md |
| Agent workflow or project pattern changes | .claude/agent-memory/MEMORY.md |
| User preferences, workflow, collaboration style | User auto-memory |
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.
- 14d ago Changed · +4 lines db8c00a1e307
- 16d ago Changed · +2 lines b067e1951d2a
- 22d ago First seen · 104 lines · 19 tokens per session scan A ab6af9ea1b48
sova-extract-knowledge is a skill published in the GitHub repository xsovad06/sova (2 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 1,246 once invoked, about $0.0001 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-10-08.
Other skills, from other repositories
reflect
Use Recall Reflect to review AI coding workflow history as a conversation-first timeline and discuss observed patterns before changing behavior. Trigger when the user asks to reflect on a project, review AI coding workflow, inspect workflow friction, discuss repeated corrections, review handoffs, or explore possible…
feature-knowledge
Structures codebase exploration into a feature knowledge base.
performance
This skill should be used when reviewing code for N+1 queries or memory leaks.
rust
This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "traits", or discusses memory safety.
agent-references
Agent-owned reference files, read by explicit path, never preloaded.
context-engineering
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.