run-history-skill-builder

run-history-skill-builder is a skill for Codex from dongshuyan/compass-skills. It costs 95 tokens per session (1,514 once invoked), scanned A, original, MIT.

A skill for turning a completed task, browser flow, or failure-recovery record into a reusable skill package or design plan.

In plain words
What is it for?
Extracting reusable instructions from run histories, artifact pipelines, and refined workflows, then packaging or reviewing the resulting skill design.
Why use it?
It captures lessons from real work so an agent can repeat a useful workflow more consistently.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions Claude Code; mentions Codex; $skill-name invocation.

Good fit Extracting reusable instructions from run histories, artifact pipelines, and refined workflows, then packaging or reviewing the resulting skill design.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dongshuyan/compass-skills/run-history-skill-builder
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 dongshuyan/compass-skills --skill run-history-skill-builder
Clone the repo
git clone --depth 1 https://github.com/dongshuyan/compass-skills

Made for: Codex.

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 run-history-skill-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/dongshuyan/compass-skills/run-history-skill-builder/github.svg)](https://agentmods.dev/skills/dongshuyan/compass-skills/run-history-skill-builder)
Your own site
<a href="https://agentmods.dev/skills/dongshuyan/compass-skills/run-history-skill-builder"><img src="https://agentmods.dev/badge/skills/dongshuyan/compass-skills/run-history-skill-builder/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 run-history-skill-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/dongshuyan/compass-skills/run-history-skill-builder"><img src="https://agentmods.dev/badge/skills/dongshuyan/compass-skills/run-history-skill-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,514 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00095 $0.01514
Opus 5 $0.00048 $0.00757
Sonnet 5 $0.00019 $0.00303
Haiku 4.5 $0.00010 $0.00151

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

Security

Grade A, and why

run-history-skill-builder 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.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/test_validate_skill_package.py, scripts/validate_skill_package.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/run-history-skill-builder/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run History Skill Builder

Language Policy

Write all user-facing output in the user's language. Default to Chinese when the language is unknown.

Role

Turn real run history into a new skill package, a plan-only skill design, or an upgrade handoff when the request is actually about an existing skill.

Portability

This skill is agent-agnostic. It should work in Codex, Claude Code, OpenCode, OpenClaw, Hermes, and similar local agent hosts that can read SKILL.md plus optional references/, scripts/, evals/, and agents/.

  • Resolve <skill-dir> from the directory that contains this SKILL.md.
  • Let <python> mean the host's available Python launcher: python3, python, or py -3.
  • Do not assume a fixed skill root, shell, home-directory layout, or path separator.
  • Placeholder paths such as <skill-dir>/scripts/... describe path segments, not a required separator style. On Windows, use the separator style that your shell or harness accepts.
  • Before writing files, lock the output directory. If the user does not provide one, propose a neutral local target such as the current repository's skills/ directory or the host agent's documented local skills directory, then wait for confirmation.

Workflow

  1. Lock intent: decide whether the request is plan_only, new_single_skill, router_skill, skill_suite, or existing_skill_upgrade_handoff.
  2. Lock evidence scope: confirm which conversation turns, files, logs, artifacts, diffs, browser flows, or transcripts you may read.
  3. Lock output location before writing files.
  4. Reconstruct the workflow from authorized evidence: user goal, real steps, failures, fixes, success proofs, and approval gates.
  5. Mine local or open-source patterns only when they help package the workflow more reliably.
  6. Separate reusable invariants from local accidentals such as one-time paths, account names, one-day product quirks, or temporary user preferences.
  7. Abstract the workflow into state gates, validation gates, scripts, references, examples, and evals. Delete weak routes that depend on subjective guesses.
  8. Choose the smallest package that preserves correctness.
  9. Write the skill only after the previous gates are satisfied.
  10. Validate, report remaining assumptions, and hand the package back with paths and checks.

Read the full file on GitHub · 122 lines

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 · 122 lines · 95 tokens per session scan A a997f6d7de4f

Subscribe to this mod's changes

run-history-skill-builder is a skill published in the GitHub repository dongshuyan/compass-skills (725 stars, last pushed 17d ago), licensed MIT. It adds 95 tokens to every session and 1,514 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-30.

Related

Other skills, from other repositories

install-memu

Install or uninstall memU for whatever agent you are — identify your host, print its packaged guide, and follow it to wire (or unwire) both seams (record and inject). Use when the user asks to install, set up, integrate, remove, or uninstall memU.

NevaMind-AI/memU · 61 tokens

lore

Long-term Markdown project memory for AI coding agents. Use when the user wants to record, recall, audit, sync, or compress project decisions, architecture, conventions, monorepo scopes, or .lore/ entries, including natural-language requests like "remember this decision" or explicit lore…

TheaDust/lore · 141 tokens

fleet-conductor

Use when conducting a large backlog or multi-repository campaign across several worker lanes, especially when work needs bounded ownership, held dependencies, collision control, draft pull request gates, and evidence-based landing. Triggers on "conduct the fleet", "burn down the backlog", "run a multi-repo campaign"…

escoffier-labs/skillet · 73 tokens

demi

Use before implementing, scaffolding, prototyping, or adding a feature when the work should start with the smallest useful code path, avoid speculative architecture, or prevent overbuilding before reduce would be needed.

escoffier-labs/skillet · 43 tokens

stagiaire

Use when the current session needs an answer or a work product from a model on ANOTHER vendor's stack - a second opinion from a different model family, a cheap fast model for bulk work, or a cross-model review - by dispatching that vendor's own CLI as a one-shot worker. Triggers include "ask…

escoffier-labs/skillet · 133 tokens

using-skillet

Use when starting any conversation - establishes how to find and use skillet skills, requiring skill invocation before ANY response including clarifying questions.

escoffier-labs/skillet · 31 tokens