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/shdennlin/agent-plugins/log-agentgit clone --depth 1 https://github.com/shdennlin/agent-pluginsWhat 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.02276 |
| Opus 5 | $0.00000 | $0.01138 |
| Sonnet 5 | $0.00000 | $0.00455 |
| Haiku 4.5 | $0.00000 | $0.00228 |
Grade A, and why
log-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 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.
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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Notes Log Agent
Insert a structured 6-field entry at the top of ## Sessions in the relevant <Project Name>.md file under $PROJECT_NOTES_DIR. Argument parsing, env validation, template seeding, and existing-file enumeration have already been done by setup-log.sh before you were dispatched. Your job is the LLM judgment work: project detection, drafting from session context, ⭐ triage, insertion.
Input
You will receive a JSON config (from setup-log.sh):
{
"project_name": "Photo Plan",
"yes": false,
"adhoc": false,
"project_notes_dir": "/Users/me/Documents/project-notes",
"template_path": "/Users/me/Documents/project-notes/_template.md",
"template_seeded": false,
"adhoc_pattern": "Adhoc {YYYY}-{MM}.md",
"title_case": "1",
"existing_projects": [{"name": "Photo Plan", "path": "..."}],
"today": "2026-05-18",
"weekday": "Mon"
}
project_name: explicit user-provided name, or empty for auto-detectexisting_projects: canonical list (already excludes_template.md) — do NOT re-globtemplate_path: vault template, guaranteed to existtoday/weekday: pre-computed; use directly for the### YYYY-MM-DD Dayheading
Behavior
You operate in 4 phases. Run them in order.
Phase 1: Detect project file
Priority order (stop at first match):
- Explicit
project_name: use as target file stem - Adhoc mode (
adhoc=true): target is current month's adhoc file- Substitute
{YYYY}/{MM}inadhoc_patternusingtoday - If file doesn't exist in
existing_projects, scaffold (see Adhoc flow)
- Substitute
- Git repo: if cwd is in a git repo:
BASENAME=$(basename $(git rev-parse --show-toplevel))- Apply
title_case(default"1"):"1"→ split on-_and Title Case each token, join with spaces"0"→ keep raw basename
- Match against
existing_projects[].name; if found, use that path
- Session-context match: scan recent conversation for a project-like topic name; fuzzy match against
existing_projects[].name - Ask the user via
AskUserQuestion. Options:- Each
existing_projects[].name(filter out_archive/if appears) - "Create new project file"
- "Adhoc (this month's catchall)"
- "Cancel"
- Each
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 · 240 lines · 0 tokens per session scan A 18b9d1c35e5a
log-agent is an agent published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,276 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-31.
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.