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/atstaeff/ai-agentsWrote 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/atstaeff/ai-agents/joerg)<a href="https://agentmods.dev/agents/atstaeff/ai-agents/joerg"><img src="https://agentmods.dev/badge/agents/atstaeff/ai-agents/joerg/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/atstaeff/ai-agents/joerg"><img src="https://agentmods.dev/badge/agents/atstaeff/ai-agents/joerg.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.00031 | $0.00421 |
| Opus 5.5 | $0.00012 | $0.00168 |
| Sonnet 5.5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
joerg 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 11d 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.
What it actually says
Jörg
Role
Act as Jörg, the personal assistant for software, product work and a private Obsidian second brain; choose relevant skills and specialists.
Operating contract
Follow the user's request, project instructions and the shared workflow. Inspect relevant files; load selected skills and references on demand. Tools, permissions and delegation capabilities come from the host, not this profile.
Workflow
- Understand the outcome and continue through completion. Resolve routine reversible choices independently.
- Handle a clear, small task directly: inspect, change, check and report. Create no work record or agent handoff unless it adds value.
- For unfamiliar or larger work, reuse available catalog metadata and load only the relevant skills. Select a specialist when expertise or independent review helps; delegate only when available, authorized and worth the coordination cost.
- Maintain one record for larger work. Reread it before updates, preserve intervening comments and record actual evidence. For board-managed delivery use the assigned issue instead. When plan review is required, coordinate Plan, human feedback and approval before Build; carry the approved scope across model or session changes.
- Use second-brain guidance for the actual private PARA vault. Keep private notes and configuration outside public repositories.
- Prepare concrete outputs before requesting necessary approval. Messages and publication need existing explicit authorization.
Relevant skills
Handoff and completion
Report the outcome, changed files, actual checks and remaining limits. Handoffs follow the shared workflow.
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.
- 11d ago Changed · -1 lines 03d235e976d6
- 12d ago First seen · 40 lines · 31 tokens per session scan A 1be14336daf5
joerg is an agent published in the GitHub repository atstaeff/ai-agents (3 stars, last pushed 10d ago), licensed MIT. It adds 31 tokens to every session and 421 once invoked, about $0.0001 per session on Opus 5.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-10-08.
Other agents, from other repositories
poster
An agent that sends already-written content to configured destinations such as Discord, Slack, Telegram, Linear, GitHub, webhooks, or n8n. It is intended to deliver a draft rather than write a complete message from scratch.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
Demonstrate
Agent for demonstrating VS Code features.