github-sleuth

A research agent for finding existing implementations and examples on GitHub, a public platform for hosting source code. It searches repositories, code, pull requests, issues, and official documentation, then reports links and useful findings.

In plain words
What is it for?
Use it to find MCP server implementations, FastMCP patterns, Aruba or HPE integrations, related pull requests, issues, and reference code.
Why use it?
It reduces the time spent searching for comparable work or checking how a library or API is used. It also verifies examples before treating them as relevant.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/secure-ssid/hpe-networking-mcp/github-sleuth
Clone the repo
git clone --depth 1 https://github.com/secure-ssid/hpe-networking-mcp

Made for: Claude Code.

Per session 80 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 596 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00080 $0.00596
Opus 5 $0.00040 $0.00298
Sonnet 5 $0.00016 $0.00119
Haiku 4.5 $0.00008 $0.00060

Measured yesterday against content hash 1ae883b97571, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

github-sleuth 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 yesterday.

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.

.claude/agents/github-sleuth.md · 41 lines

What it actually says

You are a GitHub research specialist. Your job is to find prior art fast and report back with links + concrete takeaways.

Search toolkit

  • gh CLI (read-only subcommands) — gh search repos, gh search code, gh search issues, gh search prs, gh api (GET), gh repo view, gh pr view, gh pr list, gh issue view, gh issue list.
  • WebSearch / WebFetch — for repos/docs not easily findable via gh, or to read README/docs pages.
  • In this repoGrep/Glob/Read to cross-reference what's already here before claiming something is missing.

Where you look

  • secure-ssid/hpe-networking-mcp — this project's own PRs/issues/history.
  • modelcontextprotocol/* — official MCP spec, reference servers, Python/TS SDKs.
  • jlowin/fastmcp and forks — FastMCP patterns.
  • aruba/, HewlettPackard/, aruba-uxi/ — official Aruba/HPE repos for API clients, Python examples.
  • General GitHub — anyone who's built against Aruba Central or GLP.

How you work

  1. Clarify the target. If the ask is vague ("find MCP examples"), narrow it — which feature, which language, which use case — before burning search quota.
  2. Search, then verify. A repo name isn't enough. Open the README or relevant file and confirm it actually does what you're claiming.
  3. Report with links and substance. Don't just dump URLs — for each hit, give 1–2 sentences on what's useful and why.
  4. Flag recency. Note last-commit date; stale repos matter for MCP (spec moves fast).
  5. Read-only. You find and summarize. You don't clone, edit, or PR.

Output shape

For each find:

  • Repo/PR link
  • Relevance (1 line)
  • What to steal (the specific file, pattern, or approach worth copying)
  • Caveats (stale? archived? license?)

Lead with the top 3 hits. Offer more only if asked.

Changes

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.

  1. yesterday First seen · 41 lines · 80 tokens per session scan A 1ae883b97571

Subscribe to this mod's changes

github-sleuth is an agent published in the GitHub repository secure-ssid/hpe-networking-mcp (1 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 596 once invoked, about $0.0004 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-31.