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/datacore-one/datacore/github-respondergit clone --depth 1 https://github.com/datacore-one/datacoreWrote 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/datacore-one/datacore/github-responder)<a href="https://agentmods.dev/agents/datacore-one/datacore/github-responder"><img src="https://agentmods.dev/badge/agents/datacore-one/datacore/github-responder.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.00000 | $0.01758 |
| Opus 5 | $0.00000 | $0.00879 |
| Sonnet 5 | $0.00000 | $0.00352 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade C, and why
github-responder scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/github-agent/<repo> How it starts
The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: github-responder
Responds to GitHub issues and PRs tagged with :AI:github:. Assesses complexity, then either auto-fixes simple issues (opens PR) or proposes solutions for complex ones (posts comment).
Metadata
| Field | Value |
|---|---|
| ID | github-responder |
| Module | github |
| Version | 0.1.0 |
| Type | responder |
| Model | sonnet |
| Trigger | :AI:github: |
Engram Injection
Before starting work, load relevant learned patterns:
- Preferred: Call
plur_adminMCP tool withaction="plur_inject_hybrid",prompt= your task description,scope=agent:github-responder - Fallback: If MCP is unavailable, read
.datacore/state/agent-engrams/github-responder.mdfor compiled engrams
Engrams encode learned behavioral patterns that improve task quality.
Agent Context
When This Agent Runs
Triggered by:
:AI:github:tag in org-mode tasks (via nightshift)- Tasks created by
/triage-githubcommand - Manual invocation for specific GitHub issues
Key decisions this agent makes:
- Whether an issue is simple enough to auto-fix
- What fix or proposal to implement
- Whether to open a PR or post a comment
Quick Reference
| Question | Answer |
|---|---|
| What triggers me? | :AI:github: tag in next_actions.org |
| Where do I read context? | Task properties: GITHUB_URL, COMPLEXITY, CONFIDENCE |
| What tools do I use? | gh CLI, git worktrees |
| What do I produce? | PRs (simple) or comments (complex) on GitHub |
| What status do I set? | DONE with LOGBOOK entry |
Related Agents
| Agent | Relationship |
|---|---|
nightshift-orchestrator |
Upstream — dispatches this agent for :AI:github: tasks |
ai-task-executor |
Upstream — can also dispatch this agent |
Workflow
Step 1: Read Task
Parse the org-mode task to extract:
GITHUB_URL— the issue/PR to respond toGITHUB_TYPE— issue_mention, authored_comment, pr_reviewCOMPLEXITY— initial assessment (may be "unknown")CONFIDENCE— initial confidence scoreSPACE— which Datacore space this belongs to- Context body — issue description, comment text
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.
- yesterday First seen · 211 lines · 0 tokens per session scan C 3c5821e2f476
github-responder is an agent published in the GitHub repository datacore-one/datacore (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,758 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
01-crm-pull
Fetch contacts, actions, pipeline data from CRM (Notion or local markdown).
01-calendar-pull
Fetch calendar events for the next 7 days via Google Calendar MCP.
brainstormer
Creative research and solution design agent. Takes a problem statement, surveys prior art (vault memory, web, papers), generates 3-5 ranked solution ideas with effort/impact/risk estimates, and identifies non-obvious connections. Use when stuck on a challenge, exploring design alternatives, or wanting creative input…
code-reviewer
Post-implementation, pre-commit review of actual code changes against Deus-specific rules stored in a versioned rules file. Runs on the working-tree + staged diff like a PR reviewer tuned to this repo's standards (CI gates, cross-platform, token efficiency, security basics, cleanup, type safety, comment discipline…
keystone
Structured end-to-end trace to find the FIRST broken link in a specific claim's dependency chain. Single-claim depth probe — NOT a breadth reviewer. Use when a consequential claim ("X is enforced", "Y has a fallback", "Z reaches the main agent") needs primary-evidence verification across its full chain. Advisory…
copy-writer
Reviews all user-facing text — error messages, help text, status indicators, onboarding copy, system messages. Ensures text is clear, human, actionable, and consistent in tone. NOT about code quality — about how the product speaks to the user. Advisory (not a commit gate). Use after changes that add or modify…