autology-workflow

autology-workflow is a skill for Claude Code from Curt-Park/autology. It costs 58 tokens per session (430 once invoked), scanned A, original, MIT.

A workflow for keeping a project's knowledge documents aligned with important decisions and completed actions. It identifies whether information should update an existing document or be recorded as a new one.

In plain words
What is it for?
Use it after significant code or process changes to classify new knowledge, update existing notes, or capture decisions in project documents.
Why use it?
It prevents project documentation from becoming outdated after commits, pull requests, or decisions about technology and process. It also links related knowledge where appropriate.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the autology plugin — 6 skills, 2 commands, 1 hook shipped together

Good fit Use it after significant code or process changes to classify new knowledge, update existing notes, or capture decisions in project documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/curt-park/autology/autology-workflow
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.

Any agent
npx skills add Curt-Park/autology --skill autology-workflow
Clone the repo
git clone --depth 1 https://github.com/Curt-Park/autology

Made for: Claude Code.

Or install autology, the plugin that ships this one along with the rest of its 6 skills, 2 commands, 1 hook.

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 autology-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/curt-park/autology/autology-workflow/github.svg)](https://agentmods.dev/skills/curt-park/autology/autology-workflow)
Your own site
<a href="https://agentmods.dev/skills/curt-park/autology/autology-workflow"><img src="https://agentmods.dev/badge/skills/curt-park/autology/autology-workflow/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.

agentmods 80×15 button for autology-workflow

Your own site · 80×15
<a href="https://agentmods.dev/skills/curt-park/autology/autology-workflow"><img src="https://agentmods.dev/badge/skills/curt-park/autology/autology-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 430 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00058 $0.00430
Opus 5 $0.00029 $0.00215
Sonnet 5 $0.00012 $0.00086
Haiku 4.5 $0.00006 $0.00043

Measured 12d ago against content hash 500bc0dec8ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

autology-workflow 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 12d 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/autology-workflow/SKILL.md · 42 lines

What it actually says

Overview

Route to the right autology skill after significant actions. Knowledge captured close to the action is more accurate and complete — this workflow keeps docs/ in sync with what actually happened.

Trigger Points

[Action completed] After commit/push/PR or decision/convention discovered

  1. /autology:triage-knowledge — context triage: analyze action, return classified list + topology hints
  2. In parallel from the same triage result:
    • Existing items → batch /autology:sync-knowledge (use topology hints to verify connected nodes too)
    • New items → batch /autology:capture-knowledge (use suggested relations from hints to add wikilinks)

If triage returns only new items (no existing matches), skip sync — capture runs alone. If triage returns only existing items (nothing new), skip capture — sync runs alone.

Signals for "action completed":

  • commit, push, PR created
  • "decided", "chose", "always", "never", "the rule is", any architectural choice

autology-workflow just completed (skip — do not re-trigger):

  • triage-knowledge, sync-knowledge, or capture-knowledge just ran
  • docs/*.md file was just written or edited

Flow

Action → triage → sync (existing) + capture (new) → done

Common Mistakes

Mistake Fix
sync/capture without triage first Without triage + hints, risk duplicates or missing nodes
Ignore topology hints in sync/capture Use connected/suggested relations to strengthen wikilinks
Only capture when user says "remember" Self-discovered conventions are also capture targets
Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 12d ago First seen · 42 lines · 0 tokens per session scan A 500bc0dec8ac

Subscribe to this mod's changes

autology-workflow is a skill published in the GitHub repository Curt-Park/autology (24 stars, last pushed 6mo ago), licensed MIT. It adds 58 tokens to every session and 430 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

okf-pro

Operating rules for the .okf/ knowledge bundle — filing new concepts, the board, the journal, the daily snapshot, closing work, source attribution, and the generated/verified attestation policy. Use before reading from or writing anything into .okf/.

serradura/okf · 56 tokens

mama-context

Always-on background context injection from MAMA memory. Automatically surfaces relevant decisions when you work on code, without explicit invocation.

jungjaehoon-lifegamez/MAMA · 28 tokens

mama-install

Install MAMA OS and follow its self-teaching CLI until the first report is confirmed.

jungjaehoon-lifegamez/MAMA · 22 tokens

project-sync

On-demand AI-powered sync of a project's repo state into the brain vault. Reads live git/GitHub/Jira data, updates the project status doc, and makes targeted edits to relevant brain docs where content is clearly stale. Triggered by "/project-sync [name]", "sync [project]", "what's the current state of [project]".

michaeljauk/brain-starter · 73 tokens

hmem-activate

Switch active project mid-session via loadproject, then fix any misrouted O-entry exchanges. Use when the user says 'aktiviere/lade Projekt X', 'switch to project Y', or whenever you'd otherwise call loadproject mid-session.

Bumblebiber/hmem · 54 tokens

guardian-memory

Maintain project context in Project Guardian's memory.db knowledge graph. Use during coding, debugging, planning, and project-management sessions to restore relevant context and record significant decisions, changes, tasks, and milestones.

1999AZZAR/project-guardian-mcp-server · 43 tokens