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 archimedes-run/omniHarness --skill github-deep-researchgit clone --depth 1 https://github.com/archimedes-run/omniHarnessWrote 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/archimedes-run/omniharness/github-deep-research)<a href="https://agentmods.dev/skills/archimedes-run/omniharness/github-deep-research"><img src="https://agentmods.dev/badge/skills/archimedes-run/omniharness/github-deep-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/archimedes-run/omniharness/github-deep-research"><img src="https://agentmods.dev/badge/skills/archimedes-run/omniharness/github-deep-research.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.01250 |
| Opus 5.5 | $0.00027 | $0.00500 |
| Sonnet 5.5 | $0.00014 | $0.00250 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
github-deep-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.
This is a copy
100% identical to github-deep-research — 0 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Deep Research Skill
Multi-round research combining GitHub API, web_search, web_fetch to produce comprehensive markdown reports.
Research Workflow
- Round 1: GitHub API
- Round 2: Discovery
- Round 3: Deep Investigation
- Round 4: Deep Dive
Core Methodology
Query Strategy
Broad to Narrow: Start with GitHub API, then general queries, refine based on findings.
Round 1: GitHub API
Round 2: "{topic} overview"
Round 3: "{topic} architecture", "{topic} vs alternatives"
Round 4: "{topic} issues", "{topic} roadmap", "site:github.com {topic}"
Source Prioritization:
- Official docs/repos (highest weight)
- Technical blogs (Medium, Dev.to)
- News articles (verified outlets)
- Community discussions (Reddit, HN)
- Social media (lowest weight, for sentiment)
Research Rounds
Round 1 - GitHub API
Directly execute scripts/github_api.py without read_file():
python /path/to/skill/scripts/github_api.py <owner> <repo> summary
python /path/to/skill/scripts/github_api.py <owner> <repo> readme
python /path/to/skill/scripts/github_api.py <owner> <repo> tree
Available commands (the last argument of github_api.py):
- summary
- info
- readme
- tree
- languages
- contributors
- commits
- issues
- prs
- releases
Round 2 - Discovery (3-5 web_search)
- Get overview and identify key terms
- Find official website/repo
- Identify main players/competitors
Round 3 - Deep Investigation (5-10 web_search + web_fetch)
- Technical architecture details
- Timeline of key events
- Community sentiment
- Use web_fetch on valuable URLs for full content
Round 4 - Deep Dive
- Analyze commit history for timeline
- Review issues/PRs for feature evolution
- Check contributor activity
Report Structure
Follow template in assets/report_template.md:
- Metadata Block - Date, confidence level, subject
- Executive Summary - 2-3 sentence overview with key metrics
- Chronological Timeline - Phased breakdown with dates
- Key Analysis Sections - Topic-specific deep dives
- Metrics & Comparisons - Tables, growth charts
- Strengths & Weaknesses - Balanced assessment
- Sources - Categorized references
- Confidence Assessment - Claims by confidence level
- Methodology - Research approach used
What ships with it
2 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 First seen · 167 lines · 68 tokens per session scan A 7add6956b424
github-deep-research is a skill published in the GitHub repository archimedes-run/omniHarness (7 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 1,250 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to github-deep-research, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
memory-import
Bulk-import an external knowledge base into Prismer memory via the three-layer import pipeline (07 §3.1). Use when the user asks to import/migrate documents, a knowledge base, or notes into workspace memory. Layer 1 lands raw documents (zero LLM, instantly searchable); Layer 2 is YOUR distillation work — you read the…
cli-creator
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a…
sora-taira-testnet
Work against the SORA Taira testnet through its deployed Torii MCP endpoint for live account, asset, alias, contract, governance, Musubi package-registry, and transaction workflows. Use when Codex needs to inspect or mutate the Taira testnet, verify or add https://taira.sora.org/v1/mcp, prefer the curated iroha. tool…
gateway
Start and manage the Kurtosis gateway for Kubernetes. The gateway forwards local ports to the Kurtosis engine and services running in a k8s cluster. Required when using Kurtosis with Kubernetes. Use when kurtosis engine status shows nothing on k8s or services aren't reachable.