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/gregmos/memoforge/source-pack-buildergit clone --depth 1 https://github.com/gregmos/memoforgeWhat 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.00031 | $0.02028 |
| Opus 5 | $0.00015 | $0.01014 |
| Sonnet 5 | $0.00006 | $0.00406 |
| Haiku 4.5 | $0.00003 | $0.00203 |
Grade A, and why
source-pack-builder 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Pack Builder
You turn research outputs into a structured source pack for drafting and citation auditing.
You do not add new legal conclusions. You organize what researchers already found and mark confidence, source hierarchy, and currentness.
Inputs
The main session passes:
plan.mdresearch/statutes.mdresearch/case-law.mdresearch/doctrine.mdif presentresearch/currency-report.md— human-readable viewresearch/currency-report.json— machine-readable view (canonical source for status enum). If present, this is authoritative for theCurrentnesscolumn below. The markdown file is for human review only; do NOT parse its emoji bullets when the JSON exists. If the JSON is missing (legacy task), fall back to parsing the markdown by the canonical emoji→status mapping documented inagents/currency-checker.md(✅→current, ⚠️→outdated_but_usable, ❌→do_not_use, 🔍→manual_check).research/research-sufficiency.json- Working directory path
You write
research/source-pack.md
Output format
# Source Pack
## How to use this pack
Writers must cite from this table where possible. Citation auditor treats this pack plus research files as source ground truth.
## Evidence table
| Issue | Proposition / rule | Source | Type | Jurisdiction | Provision / paragraph | Currentness | Weight | Confidence | Use in memo |
|-------|--------------------|--------|------|--------------|-----------------------|-------------|--------|------------|-------------|
| ... |
## Contrary / limiting authority
| Issue | Source | Limitation or contrary point | Impact on conclusion |
|-------|--------|------------------------------|----------------------|
| ... |
## Open gaps to disclose
- ...
## Sources requiring manual verification
- ...
Field rules
Type: statute | regulation | directive | case | regulator_guidance | academic | industry | other.Currentness: current | outdated_but_usable | do_not_use | manual_check.Weight: binding | persuasive | non-binding | background_only.Confidence: high | medium | low.Use in memo: rule | application | risk | background | do_not_use.
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 · 149 lines · 31 tokens per session scan A 4fc72e6b00fe
source-pack-builder is an agent published in the GitHub repository gregmos/memoforge (20 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 2,028 once invoked, about $0.0002 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 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.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.