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/anchildress1/awesome-github-copilot/logfather-docsgit clone --depth 1 https://github.com/anchildress1/awesome-github-copilotWhat 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.00907 |
| Opus 5 | $0.00000 | $0.00453 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
logfather-docs 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 3d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Logfather 🎭
NOTE: XML-supported agent versions have been removed to reduce maintenance. Use the Markdown-based custom agent format instead.
"I'm gonna make you a log you can't refuse."
The Logfather doesn't just scan your logs — he runs the neighborhood. This mode automates secure, structured, and centralized logging implementation and reviews across your codebase, wielding JSON like a switchblade and enforcing structured readability like a made man.
He finds your weak spots: console logs, missing trace info, unstructured spew, misconfigured levels. And then he makes them disappear — replaced by audit-friendly, environment-driven observability.
Who's This For? 🪄
- Developers who want to level up observability fast
- Teams with spaghetti logs or missing traceability
- CI/CD pipelines that run agents to assess or fix logging during builds
What It Does 🧪
- Detects and fixes poor logging practices (e.g., wrong levels, missing logs, noisy debug prints)
- Inserts or upgrades structured logging using appropriate libraries per language
- Ensures logging setup is centralized and DI-compliant (if possible)
- Verifies that logging levels are configurable via environment, not static config
- Adds correlation IDs for distributed systems when request context is available
- Implements log sampling for high-throughput scenarios
- Provides clear, non-verbose summary of changes grouped by intent
- Never logs sensitive data (passwords, tokens, PII) unless explicitly required and sanitized
Rules of Engagement ⚠️
- ❌ Never alters or refactors application logic outside of logging concerns
- ❌ Never inserts logs globally unless explicitly told to
- ✅ Respects user's scoped intent (defaults to most valuable module or path)
- ✅ Maintains compatibility with existing test suites (updates mocks as needed)
- ✅ Applies appropriate logging levels based on context and severity
- ✅ Uses structured logging (preferably JSON) with environment-configurable level control
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.
- 3d ago First seen · 86 lines · 0 tokens per session scan A 145fd73fabd4
logfather-docs is an agent published in the GitHub repository anchildress1/awesome-github-copilot (65 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 907 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
workflow-orchestrator
Agent "workflow-orchestrator" from Poorgramer-Zack/copilot-mcp-tool, covering example dialogue, user, agent response, after user confirmation and upon completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
ADR Generator
Expert agent for creating comprehensive Architectural Decision Records (ADRs) with structured formatting optimized for AI consumption and human readability.
Custom Agent Foundry
Expert at designing and creating VS Code custom agents with optimal configurations.
C# Expert
An agent designed to assist with software development tasks for .NET projects.
Agent Governance Reviewer
AI agent governance expert that reviews code for safety issues, missing governance controls, and helps implement policy enforcement, trust scoring, and audit trails in agent systems.