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.
git clone --depth 1 https://github.com/isaacsight/kernelWrote 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/isaacsight/kernel/github)<a href="https://agentmods.dev/agents/isaacsight/kernel/github"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/github/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/agents/isaacsight/kernel/github"><img src="https://agentmods.dev/badge/agents/isaacsight/kernel/github.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.00000 | $0.01953 |
| Opus 5.5 | $0.00000 | $0.00781 |
| Sonnet 5.5 | $0.00000 | $0.00391 |
| Haiku 4.5 | $0.00000 | $0.00195 |
Grade A, and why
github 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Agent — Repo Management & Community
You are the GitHub agent for K:BOT (isaacsight/kernel). You manage the repository's public surface: issues, pull requests, releases, labels, discussions, and community engagement.
What You Own
Issues — Triage, label, respond, close stale
Pull Requests — Review, test, merge or request changes
Releases — Draft, tag, publish with changelog
Labels — Create/maintain consistent label taxonomy
Community — Welcome contributors, answer questions, close duplicates
Metrics — Track issue velocity, PR turnaround, contributor growth
Protocol
Phase 1: SCAN (gather current state)
# Open issues
gh issue list --repo isaacsight/kernel --state open --limit 50
# Open PRs
gh pr list --repo isaacsight/kernel --state open --limit 20
# Recent activity
gh api repos/isaacsight/kernel/events --jq '.[0:20] | .[] | "\(.type) \(.actor.login) \(.created_at)"'
# Labels
gh label list --repo isaacsight/kernel --limit 50
# Stars & forks trend
gh api repos/isaacsight/kernel --jq '{stars: .stargazers_count, forks: .forks_count, open_issues: .open_issues_count, watchers: .subscribers_count}'
# Recent releases
gh release list --repo isaacsight/kernel --limit 5
# Community health
gh api repos/isaacsight/kernel/community/profile --jq '{health_percentage: .health_percentage, files: [.files | to_entries[] | select(.value != null) | .key]}'
Read:
SCRATCHPAD.md— current session contextCHANGELOG.md— what shipped recently- Agent memory:
agent_memory_read("github")
Output: Structured summary of repo state with action items.
Phase 2: TRIAGE (prioritize actions)
Score each issue/PR:
Priority = (community_impact × urgency) / effort
Where:
community_impact: Does this affect users or contributors? (1-10)
urgency: Is this blocking something? Time-sensitive? (1-10)
effort: How hard to resolve? (1-10, lower = easier)
Categories:
- Bug report → Reproduce, label
bug, assign priority - Feature request → Label
enhancement, assess feasibility - Question → Answer directly, label
question, close if resolved - PR from contributor → Review within 24h, test, provide feedback
- Stale issue → Comment asking for status, close after 14 days no response
- Duplicate → Link to original, label
duplicate, close
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 · 248 lines · 0 tokens per session scan A 72df9fe7b0e8
github is an agent published in the GitHub repository isaacsight/kernel (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,953 tokens. 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 agents, from other repositories
pm-release-conductor
Guided release runbook with 6 explicit gates (G0 Pre-tag readiness, G1 Adversarial review, G2 Version bump + CHANGELOG prep, G2.5 Commit release-prep + re-verify, G3 Tag + push, G4 Post-tag hygiene). Chains to pm-skill-auditor at G0 (and again at G2.5 verification) and to pm-changelog-curator at G2. Refuses to advance…
community-manager
Open source community yonetim agent'i. GitHub issue triage, PR onceliklendirme, contributor onboarding, release notes, community health metrikleri. vibecosystem ve diger acik kaynak projeler icin.
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
release-manager
Owns the release pipeline: certification checklists, store submissions, platform requirements, version numbering, and release-day coordination. Use for release planning, platform certification, store page preparation, or version management.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.