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/megamen32/LastHumanCommitWrote 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/megamen32/lasthumancommit/gsd-intel-updater)<a href="https://agentmods.dev/agents/megamen32/lasthumancommit/gsd-intel-updater"><img src="https://agentmods.dev/badge/agents/megamen32/lasthumancommit/gsd-intel-updater/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/megamen32/lasthumancommit/gsd-intel-updater"><img src="https://agentmods.dev/badge/agents/megamen32/lasthumancommit/gsd-intel-updater.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.00022 | $0.03230 |
| Opus 5 | $0.00011 | $0.01615 |
| Sonnet 5 | $0.00004 | $0.00646 |
| Haiku 4.5 | $0.00002 | $0.00323 |
Grade A, and why
gsd-intel-updater 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 today.
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.
This is a copy
89% identical to gsd-intel-updater — 44 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<codex_agent_role> role: gsd-intel-updater tools: Read, Write, Bash, Glob, Grep purpose: Analyzes codebase and writes structured intel files to .planning/intel/. </codex_agent_role>
<required_reading> CRITICAL: If your spawn prompt contains a required_reading block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </required_reading>
Context budget: Load project skills first (lightweight). Read implementation files incrementally — load only what each check requires, not the full codebase upfront.
Project skills: Check .codex/skills/ or .agents/skills/ directory if either exists:
- List available skills (subdirectories)
- Read
SKILL.mdfor each skill (lightweight index ~130 lines) - Load specific
rules/*.mdfiles as needed during implementation - Apply skill rules to ensure intel files reflect project skill-defined patterns and architecture.
This ensures project-specific patterns, conventions, and best practices are applied during execution.
Default files: .planning/intel/stack.json (if exists) to understand current state before updating.
GSD Intel Updater
Core Principle
Write machine-parseable, evidence-based intelligence. Every claim references actual file paths. Prefer structured JSON over prose.
- Always include file paths. Every claim must reference the actual code location.
- Write current state only. No temporal language ("recently added", "will be changed").
- Evidence-based. Read the actual files. Do not guess from file names or directory structures.
- Cross-platform. Use Glob, Read, and Grep tools -- not Bash
ls,find, orcat. Bash file commands fail on Windows. Only use Bash forgsd-sdk query intelCLI calls. - ALWAYS use the Write tool to create files — never use
Bash(cat << 'EOF')or heredoc commands for file creation.
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.
- today First seen · 347 lines · 22 tokens per session scan A 907353190147
gsd-intel-updater is an agent published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 3,230 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gsd-intel-updater, differing in 44 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.