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/curie-eng/curie/github-issuesnpx skills add curie-eng/curie --skill github-issuesgit clone --depth 1 https://github.com/curie-eng/curieWhat 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.00063 | $0.00401 |
| Opus 5 | $0.00032 | $0.00200 |
| Sonnet 5 | $0.00013 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
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.
What it actually says
GitHub issue triage
When to run
The user asks about a repository's issues or pull requests — to list open issues, summarize them, find ones by label/assignee/author, or draft a new issue for review.
How to answer
- Identify the repository (
owner/repo). Ask if the user did not name one. - Call the
githubserver's tools:- list/search issues to pull the current open set,
- fetch a single issue when the user asks about one in particular.
- Summarize plainly: title, number, author, labels, and a one-line gist. Group by label or priority when triaging.
- When asked to draft an issue, write the title and body and show it for the user to confirm — do not create it unless the user explicitly says to.
Notes
github is the off-the-shelf @modelcontextprotocol/server-github stdio MCP
server, declared in this bundle's .mcp.json. It authenticates with a GitHub
personal access token read from GITHUB_PERSONAL_ACCESS_TOKEN in the sandbox
environment. That token is NOT in the bundle: you forward it at launch with
curie skill up --secret GITHUB_PERSONAL_ACCESS_TOKEN (see the README), which
passes the variable by name into the container the same way model credentials
are forwarded. A read-scoped token is enough for listing and reading; creating
an issue needs repo/issues write scope.
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 · 34 lines · 63 tokens per session scan A 7b25c3a651b9
github-issues is a skill published in the GitHub repository curie-eng/curie (35 stars, last pushed 2d ago), licensed Apache-2.0. It adds 63 tokens to every session and 401 once invoked, about $0.0003 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
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
teamharness-task-delegation
Use when a Leader turns ready Quick Task or Project Work state into Worker task instructions, sends assignment messages, checks submitted results, and defines completion/blocker report contracts. Do not use to create projects, create rooms, or execute Worker tasks.
github-workflow
Use GitHub workflow tools to read work status, draft reports, summarize follow-ups, and execute only approved issue mutations.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
dot-ai-prd-create
Create documentation-first PRDs that guide development through user-facing content.