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 skills/sonpiaz/hidrix-tools/knowledge-compilernpx skills add sonpiaz/hidrix-tools --skill knowledge-compilergit clone --depth 1 https://github.com/sonpiaz/hidrix-toolsWhat 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.00021 | $0.01056 |
| Opus 5 | $0.00010 | $0.00528 |
| Sonnet 5 | $0.00004 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
knowledge-compiler 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 2d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Compiler
Build and maintain a personal knowledge base in Obsidian vault.
Knowledge Base location
~/Documents/Obsidian Vault/07 - Knowledge Base 🧠/
├── _index.md ← Master index (auto-generated)
├── _daily-log.md ← What changed today
├── people/ ← One article per person you follow
├── concepts/ ← One article per topic/concept
├── raw/ ← Raw collected data by platform
└── output/ ← Your queries, reports, analysis
When to use
Collect + compile (full pipeline)
User says: "collect knowledge", "compile wiki", "cập nhật knowledge base", "thu thập kiến thức"
Run:
bun run ~/hidrix-tools/scripts/compile.ts
This does: collect from follow list → save to SQLite → compile wiki articles → update Obsidian.
Collect only (one person)
User says: "collect @karpathy", "thu thập bài mới của @bcherny"
Run:
bun run ~/hidrix-tools/scripts/compile.ts --user @USERNAME
Research a topic and save to wiki
User says: "research topic X và lưu vào wiki", "tìm hiểu về MCP protocol"
Steps:
- Use hidrix tools to search:
hidrix_x_search,hidrix_reddit_search,hidrix_web_search - Deep read best results:
hidrix_x_thread_reader,hidrix_reddit_thread_reader,hidrix_web_fetch - Write a concept article and save to Obsidian:
cat > ~/Documents/Obsidian\ Vault/07\ -\ Knowledge\ Base\ 🧠/concepts/CONCEPT-NAME.md << 'EOF'
# Concept Name
> Summary in 2-3 sentences
## Key Points
- Point 1
- Point 2
## Sources
- [Source 1](url)
- [Source 2](url)
## Related
- [[other-concept]]
- [[person-name]]
---
Last updated: YYYY-MM-DD
EOF
Save a single piece of content to wiki
User says: "lưu thread này vào wiki", "save this to knowledge base"
Steps:
- Read the content (thread, article, video transcript)
- Summarize key points
- Save to appropriate location:
- About a person →
people/username.md(append, don't overwrite) - About a concept →
concepts/concept-name.md - Raw data →
raw/platform/date-title.md - Analysis/query result →
output/query-title.md
- About a person →
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.
- 2d ago First seen · 135 lines · 21 tokens per session scan A 4b1544464ca1
knowledge-compiler is a skill published in the GitHub repository sonpiaz/hidrix-tools (42 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 1,056 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.