log

log is a command for coding agents from AutomateLab-tech/agency-os. It costs 0 tokens per session (192 once invoked), scanned A, original, MIT.

A command that adds a dated discussion entry to a task page.

In plain words
What is it for?
Use it to record discussion rounds and identify proposed subtasks from entries.
Why use it?
It keeps decisions and conversation history attached to the task instead of leaving them scattered across messages.

Command

Part of the agency-os plugin — 1 skill, 19 commands shipped together

Install

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.

agentmods
npx agentmods add commands/automatelab-tech/agency-os/log
Clone the repo
git clone --depth 1 https://github.com/AutomateLab-tech/agency-os

Or install agency-os, the plugin that ships this one along with the rest of its 1 skill, 19 commands.

Wrote 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.

agentmods badge for log

README.md
[![agentmods](https://agentmods.dev/badge/commands/automatelab-tech/agency-os/log.svg)](https://agentmods.dev/commands/automatelab-tech/agency-os/log)
Your own site
<a href="https://agentmods.dev/commands/automatelab-tech/agency-os/log"><img src="https://agentmods.dev/badge/commands/automatelab-tech/agency-os/log.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 192 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00192
Opus 5 $0.00000 $0.00096
Sonnet 5 $0.00000 $0.00038
Haiku 4.5 $0.00000 $0.00019

Measured 4d ago against content hash c85ae8e67e76, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

log 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 4d 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.

skills/agency-os/references/commands/log.md · 16 lines

What it actually says

Command: log <id> "<entry>"

Append a discussion entry to the task page.

  1. Sync preflight.
  2. Resolve <id>.
  3. Find or create the Discussion log toggle on the page. Append a new dated entry:
    ### <YYYY-MM-DD> — <auto-summary first 6 words of entry>
    <entry>
    
  4. Print: + Logged: [<title>](<url>).
  5. If the entry contains lines starting with + they're treated as proposed subtasks and surfaced in the output: note: detected N proposed subtasks; create with /agency-os add-subtask <id> "<title>".

The agent should call log multiple times during a discussion — once per Q/A round, or once per cohesive thought — rather than dumping a single megalogue at the end. This keeps the log queryable by date.

Changes

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.

  1. 4d ago First seen · 16 lines · 0 tokens per session scan A c85ae8e67e76

Subscribe to this mod's changes

log is a command published in the GitHub repository AutomateLab-tech/agency-os (3 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 192 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.