github-issues

An example agent bundle that reads and organizes GitHub issues and pull requests through a GitHub tool connection. It requires a GitHub personal access token, a credential that authorizes repository access.

In plain words
What is it for?
Use it to group open issues, summarize recently updated pull requests, and find bug reports needing triage in a GitHub repository.
Why use it?
It provides a ready example for repository triage without requiring the agent to implement GitHub access itself.

Plugin 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.

Claude Code
/plugin marketplace add curie-eng/curie
agentmods
npx agentmods add plugins/curie-eng/curie/github-issues
Clone the repo
git clone --depth 1 https://github.com/curie-eng/curie

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

github-issues 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.

examples/github-issues/.claude-plugin/plugin.json · 14 lines

What it actually says

{
  "name": "github-issues",
  "version": "0.1.0",
  "description": "Example bundle: an agent that reads and triages GitHub issues through the off-the-shelf GitHub MCP server, authenticated with a personal access token forwarded into the sandbox.",
  "author": { "name": "CurieTech" },
  "keywords": ["example", "mcp", "authed", "github", "stdio"],
  "secrets": ["GITHUB_PERSONAL_ACCESS_TOKEN"],
  "starterPrompts": [
    "List the open issues in curie-eng/curie and group them by label.",
    "Summarize the most recently updated pull requests in curie-eng/curie.",
    "Find open bug reports in curie-eng/curie that need triage."
  ]
}
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. 2d ago First seen · 14 lines scan A 34b1698715f0

Subscribe to this mod's changes

github-issues is a plugin published in the GitHub repository curie-eng/curie (35 stars, last pushed 2d ago), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.