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 skills/bartoszarendt/agenticloop/event-loggingnpx skills add bartoszarendt/agenticloop --skill event-logginggit clone --depth 1 https://github.com/bartoszarendt/agenticloopWrote 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/skills/bartoszarendt/agenticloop/event-logging)<a href="https://agentmods.dev/skills/bartoszarendt/agenticloop/event-logging"><img src="https://agentmods.dev/badge/skills/bartoszarendt/agenticloop/event-logging.svg" alt="Measured on agentmods" 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 | $0.00098 | $0.00960 |
| Opus 5 | $0.00049 | $0.00480 |
| Sonnet 5 | $0.00020 | $0.00192 |
| Haiku 4.5 | $0.00010 | $0.00096 |
Grade A, and why
event-logging 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.
Event logging
Event logging is optional and disabled by default. It writes local
workflow-gate events to .agenticloop/logs/<TASK-ID>.jsonl through the Node CLI.
agenticloop/AGENTIC_LOOP.md owns why event logging exists, the event taxonomy,
and which lifecycle gates emit which events. This skill owns the operational
procedure: resolving the command, honoring the disabled and non-blocking rules,
and keeping entries concise.
When event logging is off
Read .agenticloop/project.md before writing any event. Agents must not attempt
CLI event logging unless it says event_logging: enabled. When event logging is
disabled, do nothing: writing events is a no-op, and skipping them is not a
process gap.
Resolving the command
When event_logging: enabled, resolve the event logging command once per host
session before the first event write:
- If
event_logging_commandis non-empty, use that command. - If
event_logging_commandis blank or omitted, runnpx agenticloop --helponce. If it succeeds, usenpx agenticloop. - If no working event logging command is available, do not repeatedly retry and do not block the workflow. Record a truthful process gap in the task record, review, or closeout marker note, then continue.
After resolution, event writes use:
<resolved-command> event-logging <event_type> --task <TASK-ID> --role <role> --summary "<short fact>"
agenticloop event remains a compatibility alias, but new instructions should
use event-logging. Default writes target .agenticloop/logs/<TASK-ID>.jsonl
via --task <TASK-ID>; use --output <file> only for tests or an explicit local
exception. Add --outcome only for event types that require it.
Unavailable logging is always non-blocking: never fail, pause, or loop a task because event logging could not run.
Required and recommended fields
Every event needs --task <TASK-ID> (when a task is known), --role, and a
short --summary. Events in the same target that share a task_id derive the
same deterministic trace_id unless --trace-id is supplied. Use refs for
identifiers (github:issue:<n>, github:pr:<n>, commit:<sha>, branch:<name>,
task-file:<path>, command:<command>) and --data-json for small structured
context.
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 · 98 tokens per session scan A ed677eda72d8
event-logging is a skill published in the GitHub repository bartoszarendt/agenticloop (2 stars, last pushed 13d ago), licensed MIT. It adds 98 tokens to every session and 960 once invoked, about $0.0005 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-31.
Other skills, from other repositories
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
consulting-analysis
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This…
ppt-generation
Use this skill when the user requests to generate, create, or make presentations (PPT/PPTX). Creates visually rich slides by generating images for each slide and composing them into a PowerPoint file.
deerflow-maintainer-orchestrator
Use when a DeerFlow maintainer needs comment-only GitHub issue or PR handling: resolve issue/PR scopes with gh, analyze issues, post or draft issue comments, perform PR review comments, review PR or issue batches, compare competing PRs that target the same issue, give fix strategy, risk classification, and validation…
systematic-literature-review
Use this skill when the user wants a systematic literature review, survey, or synthesis across multiple academic papers on a topic. Also covers annotated bibliographies and cross-paper comparisons. Searches arXiv and outputs reports in APA, IEEE, or BibTeX format. Not for single-paper tasks — use academic-paper-review…
academic-paper-review
Use this skill when the user requests to review, analyze, critique, or summarize academic papers, research articles, preprints, or scientific publications. Supports comprehensive structured reviews covering methodology assessment, contribution evaluation, literature positioning, and constructive feedback generation.…