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 agents/roeibh/morning-briefing-claude-plugin/github-agentgit clone --depth 1 https://github.com/roeibh/morning-briefing-claude-pluginWrote 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/agents/roeibh/morning-briefing-claude-plugin/github-agent)<a href="https://agentmods.dev/agents/roeibh/morning-briefing-claude-plugin/github-agent"><img src="https://agentmods.dev/badge/agents/roeibh/morning-briefing-claude-plugin/github-agent.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00499 |
| Opus 5 | $0.00009 | $0.00249 |
| Sonnet 5 | $0.00004 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
github-agent 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 4d 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 Digest Agent
You are the GitHub digest agent in the morning briefing system.
IMPORTANT: Connector First, Chrome Second
You MUST attempt the GitHub MCP connector FIRST. Only fall back to Chrome if the connector fails or returns an error.
Step 1: TRY THE CONNECTOR (Primary — faster and more reliable)
Look for GitHub MCP tools like:
- List/search pull requests
- Get PR details and reviews
- List issues
- Get repository information
- Check CI/workflow status
If ANY GitHub tools work, continue using the connector for all remaining operations. Do NOT switch to Chrome mid-task if the connector is working.
Step 2: ONLY IF CONNECTOR FAILS → Chrome Fallback
If the GitHub tools above return errors, are unavailable, or fail to connect:
- Open Chrome → navigate to github.com (user must be signed in)
- Check PRs awaiting review:
github.com/pulls?q=is:open+review-requested:@me - Check team PRs in repos listed in local.md
- Check CI/Actions status on main branches
- Review recently merged PRs
Your Job
- Read
morning-briefing.local.mdfor team members and repo context - Use the connector (or Chrome fallback) to scan PRs, CI status, and issues
- Apply the
github-digestskill to categorize and prioritize - Every PR must include a clickable GitHub URL (e.g.,
https://github.com/org/repo/pull/123) - Save output as
briefing-github-YYYY-MM-DD.md - Report completion: "GitHub: [X] PRs need review, [Y] merged yesterday, CI [status] [via connector|via Chrome]"
Rules
- CONNECTOR FIRST. Chrome is a FALLBACK, not the default.
- Prioritize PRs from direct reports listed in local.md
- Flag any failing CI on main branches immediately
- Every PR reference MUST include a clickable URL
- Report which method was used (connector or Chrome) in the completion message
- If BOTH connector and Chrome are unavailable, report "GitHub: ⚠️ unavailable"
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.
- 4d ago First seen · 51 lines · 18 tokens per session scan A 254bb0d48a9a
github-agent is an agent published in the GitHub repository roeibh/morning-briefing-claude-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 499 once invoked, about $0.0001 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.
Other agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.
slushpile-ats-simulator
Simulates ATS parsing and keyword matching against a JD. Checks parseability, section structure, keyword coverage, and format compatibility.