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 skills add bartoszarendt/agenticloop --skill task-record-contractgit 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/task-record-contract)<a href="https://agentmods.dev/skills/bartoszarendt/agenticloop/task-record-contract"><img src="https://agentmods.dev/badge/skills/bartoszarendt/agenticloop/task-record-contract/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/skills/bartoszarendt/agenticloop/task-record-contract"><img src="https://agentmods.dev/badge/skills/bartoszarendt/agenticloop/task-record-contract.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.00065 | $0.07434 |
| Opus 5.5 | $0.00026 | $0.02974 |
| Sonnet 5.5 | $0.00013 | $0.01487 |
| Haiku 4.5 | $0.00006 | $0.00743 |
Grade A, and why
task-record-contract 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 1mo 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 — 621 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task record contract
A task record is the durable contract for one implementation task. The engineer must be able to work from the task record without guessing.
If the current role is orchestrator, route task-record creation or refinement through [[role-delegation]] instead of writing the task record directly.
Task records are stored in the configured backend:
- Files projection: one Markdown file at
.agenticloop/tasks/<TASK-ID>.md. Seeagenticloop/backends/files.md. - GitHub projection: one GitHub issue per task when the project explicitly uses
task_backend: github. Seeagenticloop/backends/github.md.
Event Logging
Event logging is optional and off by default. When enabled, follow
[[event-logging]]: emit task.created for a new record and task.updated after
material scope, criteria, check, or backend-linkage changes. Use the task id and
a concise gate fact; never copy the task body or chat into the log.
Required sections
Use agenticloop/memory/task-record.md as the canonical task-record shape.
It defines the ordered required sections and the optional Proof Pressure,
Concurrency Plan, Parallel Safety, Grouping, Source Reference,
Applicable Project Skills, and Outcome sections. New records also include
the ## Verification Attempts section with the canonical empty state from
[[verification-evidence]]. Historical records without that optional learning
section remain readable.
The ## Outcome section is optional for routine clean tasks, maintainer-filled
at closeout. It becomes conditionally required when any of these happened:
review_rounds > 1, failed or triaged checks, blocked/needs_context state, scope
drift, stale evidence, human intervention, predicted medium/high context
overflow risk, context pressure encountered, or follow-ups. It never replaces
acceptance criteria or proof pressure.
Proof pressure
Use optional ## Proof Pressure when long-running or ambiguous work could pass
locally while missing the owner's outcome. Every field must be concrete:
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.
- 1mo ago Changed · +1 lines 5643ce350e7b
- 1mo ago First seen · 620 lines · 65 tokens per session scan A d860f9453b7e
task-record-contract is a skill published in the GitHub repository bartoszarendt/agenticloop (2 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 7,434 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
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.
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
newsletter-generation
Use this skill when the user requests to generate, create, write, or draft a newsletter, email digest, weekly roundup, industry briefing, or curated content summary. Supports topic-based research, content curation from multiple sources, and professional formatting for email or web distribution. Trigger on requests…
data-analysis
Use this skill when the user uploads Excel (.xlsx/.xls) or CSV files and wants to perform data analysis, generate statistics, create summaries, pivot tables, SQL queries, or any form of structured data exploration. Supports multi-sheet Excel workbooks, aggregation, filtering, joins, and exporting results to…
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
claude-to-deerflow
Interact with DeerFlow AI agent platform via its HTTP API. Use this skill when the user wants to send messages or questions to DeerFlow for research/analysis, start a DeerFlow conversation thread, check DeerFlow status or health, list available models/skills/agents in DeerFlow, manage DeerFlow memory, upload files to…