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/source-command-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/source-command-extract-knowledge)<a href="https://agentmods.dev/skills/xsovad06/sova/source-command-extract-knowledge"><img src="https://agentmods.dev/badge/skills/xsovad06/sova/source-command-extract-knowledge.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.00019 | $0.01005 |
| Opus 5 | $0.00010 | $0.00502 |
| Sonnet 5 | $0.00004 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
Grade A, and why
source-command-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 yesterday.
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.
source-command-extract-knowledge
Use this skill when the user asks to run the migrated source command extract-knowledge.
Command Template
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: ~/.Codex/shared-knowledge/ (cross-project patterns)
Reusable patterns that apply across multiple repositories. Loaded by agent startup scripts.
Tier 1: .Codex/rules/*.md (canonical, always loaded via AGENTS.md)
Stable patterns loaded into every session via AGENTS.md. Primary destination for confirmed conventions.
Tier 2: .Codex/agent-memory/ (agent learnings, loaded by morning agent)
Lessons learned from development and review cycles. Destination for agent-specific patterns that improve autonomous development quality.
MEMORY.md: Index filecookbook.md: Topical knowledge by domain, common mistakes with occurrence counts
Tier 3: User auto-memory (~/.Codex/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.) | .Codex/rules/<domain>.md |
| ORM/framework gotchas, review lessons, recurring mistakes | .Codex/agent-memory/cookbook.md (under matching domain section) |
| Agent workflow or project pattern changes | .Codex/agent-memory/MEMORY.md |
| User preferences, workflow, collaboration style | User auto-memory |
3. Check for Duplicates
Before writing anything:
- Read the target file
- Check for existing entries about the same topic
- Update existing entries rather than adding duplicates
- Remove entries that are now outdated or wrong
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.
- yesterday First seen · 110 lines · 19 tokens per session scan A 7b408933f134
source-command-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,005 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
code-review
You are a senior code reviewer. You receive diffs via stdin.
feature-knowledge
Structures codebase exploration into a feature knowledge base.
performance
This skill should be used when reviewing code for N+1 queries, memory leaks, or I/O bottlenecks.
rust
This skill should be used when the user works with Rust files (.rs), asks about "ownership", "borrowing", "lifetimes", "Result/Option", "traits", or discusses memory safety and type-driven design. Provides patterns for ownership, error handling, type system usage, and safe concurrency.
review
Two-stage code review: spec compliance first, then code quality. Auto-triggered after implementation. Also available as /review.
totem-compiled-rules
Compiled architectural rules and lessons from the Totem knowledge base. Load this when reviewing code for pattern violations or architectural drift.