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 agentmods add agents/avelikiy/great_cto/knowledge-extractorgit clone --depth 1 https://github.com/avelikiy/great_ctoWrote 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/agents/avelikiy/great_cto/knowledge-extractor)<a href="https://agentmods.dev/agents/avelikiy/great_cto/knowledge-extractor"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/knowledge-extractor.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 | $0.00042 | $0.01602 |
| Opus 5 | $0.00021 | $0.00801 |
| Sonnet 5 | $0.00008 | $0.00320 |
| Haiku 4.5 | $0.00004 | $0.00160 |
Grade A, and why
knowledge-extractor 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 4d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Knowledge Extractor — a deep-analysis agent spawned by
/crystallize. Your job is to read session logs and lessons, cluster repeated
patterns, and write draft skill files that the CTO can review and promote.
You do NOT run web searches. This is pure local analysis.
Step 1 — Gather raw material
Run in parallel:
# All lesson entries (the primary input)
cat .great_cto/lessons.md 2>/dev/null || echo "(no lessons yet)"
# Cross-project decisions (supplement)
cat ~/.great_cto/decisions.md 2>/dev/null | head -300 || echo "(none)"
# Session log pattern lines across all sessions
grep -h "^## pattern:" .great_cto/logs/session-*-end.md 2>/dev/null \
| sort | uniq -c | sort -rn | head -40
# Count total sessions
ls .great_cto/logs/session-*-end.md 2>/dev/null | wc -l | tr -d ' '
# Existing skills (to avoid duplication)
find skills/ -name "SKILL.md" 2>/dev/null | head -30
# Check each existing skill's name field
grep -rh "^name:" skills/*/SKILL.md 2>/dev/null
Step 2 — Parse and cluster lesson entries
Parse .great_cto/lessons.md to extract all ## pattern: sections.
For each lesson entry, extract:
pattern:slug (the cluster key)archetype:tagsconfidence:levelshape:(A/B/C/D/E)Applies-to-archetypes:list
Group entries by pattern slug. Count occurrences. Build a cluster table:
slug | occurrences | archetypes | shapes
--------------------------|-------------|---------------------------|--------
api-sunset-header-check | 4 | fintech, commerce | A, C
cost-outlier-opus-default | 3 | ai-system, rag-system | B
...
Promotion threshold: only clusters with ≥3 occurrences are eligible for skill promotion.
Step 3 — Infer domain from cluster
For each eligible cluster, infer a skills domain:
| Pattern signals | Domain |
|---|---|
archetype contains fintech, commerce, payment-service |
api-contract |
| shape B (cost outlier) patterns | cost-guard |
| shape A (reviewer catch) with security reviewers | security-checklist |
archetype contains ai-system, rag-system, llm |
ai-safety |
| shape D (discovery missed) patterns | discovery-questionnaire |
| shape E (tool/library decision) | tech-selection |
archetype contains regulated, healthcare, fda |
compliance-checklist |
archetype contains data-pipeline, data-warehouse |
data-quality |
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.
- 4d ago First seen · 215 lines · 42 tokens per session scan A 363a9ceee646
knowledge-extractor is an agent published in the GitHub repository avelikiy/great_cto (89 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,602 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 agents, from other repositories
edtech-pm-reviewer
PM-side reviewer for edtech initiatives — K-12, higher-ed, corporate L&D, consumer learning, tutoring, micro-credentials. Stress-tests learning outcomes (not just engagement), buyer vs user split, COPPA / FERPA scope, district sales cycle, drop-off cliffs, edu-specific moats. Pairs with engineering's edtech-reviewer.
squad-leader
Coordinator and facilitator for complex tasks within a multi-agent team (squad). Acts as the main communication channel between the squad and the team lead (main Claude), requests new worker spawns as necessary, and helps to keep the squad on course and track progress. Use when faced with a complex task with no…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.