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 i9wa4/dotfiles --skill technical-researchgit clone --depth 1 https://github.com/i9wa4/dotfilesWrote 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/i9wa4/dotfiles/technical-research)<a href="https://agentmods.dev/skills/i9wa4/dotfiles/technical-research"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/technical-research/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/i9wa4/dotfiles/technical-research"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/technical-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.00394 |
| Opus 5.5 | $0.00026 | $0.00158 |
| Sonnet 5.5 | $0.00013 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00039 |
Grade A, and why
technical-research 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 1mo 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.
What it actually says
Technical Research
Owns evidence-based investigation: verifying claims, comparing options with sourced tradeoffs, and confirming how libraries, APIs, and tools actually behave before conclusions are relied on.
1. Discipline
- Verify information from multiple sources before presenting as fact
- Prefer official documentation over blog posts; note publication dates
- Flag confidence level (High/Medium/Low) on each finding
- Clearly separate facts from opinions and recommendations
2. Workflow
-
Clarify scope: what exactly needs to be answered?
-
Search official docs first (WebSearch + WebFetch)
-
Check GitHub repos: issues, discussions, source code for implementation details
# Clone to /tmp for analysis when needed git clone --depth 1 <repo-url> /tmp/<repo-name> -
Cross-reference: do multiple sources agree? Flag contradictions.
-
Test when possible: run code, check versions, verify claims hands-on
-
When synthesis needs categories, labels, or first-use terms before final wording, use
clarify-conceptsafter evidence acquisition and before drafting conclusions.
3. Source Priority
- Official documentation and changelogs
- Source code and GitHub issues/discussions
- Well-maintained community resources
- Blog posts (note date, may be outdated)
4. Output Format
What ships with it
3 files 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.
- 1mo ago Changed · +2 tokens per session ff0f3b5bd922
- 2mo ago First seen · 52 lines · 63 tokens per session scan A e128ce953d4c
technical-research is a skill published in the GitHub repository i9wa4/dotfiles (12 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 394 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
gui-debug
Verify a rendering or window-chrome change in any macOS GUI app unattended — find its CGWindowID via JXA, capture that window alone (with per-pixel alpha) using screencapture -l, read exact RGBA via NSBitmapImageRep, and synthesize keystrokes, chords, clicks and drags with CGEventPost. Use for…
audit
Repo audits, one mode or all (codebase, docs, process, perf, tests, threat-model, motion, SEO, debt). Triggers "audit the codebase", "full audit", "perf audit", "audit the tests", "threat model", "motion audit", "seo audit", "debt ledger".
self-review
Deliberate end-to-end review pass over a completed change, applying the laziness ladder. Invoke when the user asks for a review, or when orchestrating one. Not a routine step after every edit.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…