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 skills add timurgaleev/memex --skill strategic-readinggit clone --depth 1 https://github.com/timurgaleev/memexWrote 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/timurgaleev/memex/strategic-reading)<a href="https://agentmods.dev/skills/timurgaleev/memex/strategic-reading"><img src="https://agentmods.dev/badge/skills/timurgaleev/memex/strategic-reading.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.00055 | $0.01620 |
| Opus 5 | $0.00028 | $0.00810 |
| Sonnet 5 | $0.00011 | $0.00324 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
strategic-reading 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 8d 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.
This is a copy
86% identical to strategic-reading — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strategic-reading — Applied Analysis from Source Texts
Convention: see
conventions/quality.md(viaget_skill conventions/quality) for citation rules (every recommendation cites the source) and back-link enforcement.Convention: see
_brain-filing-rules.md(viaget_skill _brain-filing-rules) — output pages by primary subject (concepts/ for general strategy, projects/ for problem-tied playbooks).
What this is
Take a large text PLUS a specific strategic problem, produce analysis that maps the text's insights onto the problem. This is not book summarization. This is reading with a mission.
Where book-mirror personalizes a book to the reader's whole life,
strategic-reading personalizes it to ONE current problem. Same shape
(extract → analyze → mirror), different lens.
Canonical example: a power-dynamics history book read against a specific gatekeeper-vs-incumbent fight, producing a tactical analysis that maps the book's playbook onto the situation with counter-tactics and a short/medium/long-term playbook.
Inputs
- Source text — book (EPUB/PDF), article, transcript, historical case study, any large document.
- Strategic problem — the specific situation to analyze through the lens of the text. The user describes this explicitly or it's obvious from context.
Output
The brain page is the artifact. PDF is a rendering, never primary.
Brain page structure
# [Source Title] — Applied to [Problem]
> One-paragraph executive summary: how the source maps to the situation,
> the key insight, the bottom line.
## The Core Parallel
How the source's central dynamic maps onto the user's situation.
## Chapter / Section Triage
For each major section of the source:
- 2-3 sentence summary of what it says
- Relevance to the problem: HIGH / MEDIUM / LOW
- One directly applicable quote (if any)
## The Source's Playbook
The author's framework, tactics, or strategies — organized as:
- What the protagonist DID (tactics)
- What WORKED and why
- What FAILED and why
- What OPPONENTS did that was effective
## Counter-Tactics
Specific moves from the source that map to the user's situation:
- What to DO (with source evidence)
- What to AVOID (with source evidence)
- What to WATCH FOR (warning signs from the source)
## Applied Playbook
The synthesis — actionable recommendations:
- **Short-term** (this week / this month)
- **Medium-term** (this quarter)
- **Long-term** (this year+)
## Key Quotes
Direct quotes from the source that are devastatingly relevant.
Maximum 5-10. Quality over quantity.
## See Also
Links to relevant brain pages (related concepts, related projects).
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.
- 8d ago First seen · 191 lines · 55 tokens per session scan A 74d6585178cb
strategic-reading is a skill published in the GitHub repository timurgaleev/memex (8 stars, last pushed today), licensed MIT. It adds 55 tokens to every session and 1,620 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to strategic-reading, differing in 42 lines, and is treated as a copy.
Other skills, from other repositories
design-mcp-server
Design the tool surface, resources, and service layer for a new MCP server. Use when starting a new server, planning a major feature expansion, or when the user describes a domain/API they want to expose via MCP. Produces a design doc at docs/design.md that drives implementation.
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, and produces a tight report with concrete findings and numbered follow-up options. Use after adding or modifying definitions, or when the user asks to…
maintenance
Investigate, adopt, and verify dependency updates — with special handling for @cyanheads/mcp-ts-core. Captures what changed, understands why, cross-references against the codebase, adopts framework improvements, syncs project skills, and runs final checks. Supports two entry modes: run the full flow end-to-end, or…