curate-delta

curate-delta is a skill for Claude Code from jmanhype/claude-code-plugin-marketplace. It costs 26 tokens per session (3,038 once invoked), scanned A, original, MIT.

A skill that turns feedback about an agent run into proposed updates for a shared playbook, a set of reusable instructions.

In plain words
What is it for?
Use it to review proposed playbook rules, check that they are actionable and evidence-based, and return structured additions and usage updates.
Why use it?
It helps separate useful, repeatable lessons from one-off feedback and duplicate guidance.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the ace-context-engineering plugin — 3 skills shipped together

Good fit Use it to review proposed playbook rules, check that they are actionable and evidence-based, and return structured additions and usage updates.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jmanhype/claude-code-plugin-marketplace/curate-delta
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 jmanhype/claude-code-plugin-marketplace --skill curate-delta
Clone the repo
git clone --depth 1 https://github.com/jmanhype/claude-code-plugin-marketplace

Made for: Claude Code.

Or install ace-context-engineering, the plugin that ships this one along with the rest of its 3 skills.

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 curate-delta

README.md
[![agentmods](https://agentmods.dev/badge/skills/jmanhype/claude-code-plugin-marketplace/curate-delta/github.svg)](https://agentmods.dev/skills/jmanhype/claude-code-plugin-marketplace/curate-delta)
Your own site
<a href="https://agentmods.dev/skills/jmanhype/claude-code-plugin-marketplace/curate-delta"><img src="https://agentmods.dev/badge/skills/jmanhype/claude-code-plugin-marketplace/curate-delta/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 curate-delta

Your own site · 80×15
<a href="https://agentmods.dev/skills/jmanhype/claude-code-plugin-marketplace/curate-delta"><img src="https://agentmods.dev/badge/skills/jmanhype/claude-code-plugin-marketplace/curate-delta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,038 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.00026 $0.03038
Opus 5 $0.00013 $0.01519
Sonnet 5 $0.00005 $0.00608
Haiku 4.5 $0.00003 $0.00304

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

Security

Grade A, and why

curate-delta 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 9d 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.

plugins/ace-context-engineering/skills/curate-delta/SKILL.md · 415 lines

How it starts

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

Curate Delta Proposal

You are the Curator component of the ACE (Agentic Context Engineering) system. Your role is to synthesize insights from the Reflector into structured, high-quality delta proposals that will update the playbook through deterministic merging.

Input Format

You will receive Reflector output containing:

  • Task metadata (instruction, apps, outcome)
  • Execution feedback (success/failure, error analysis)
  • Proposed bullets from Reflector
  • Existing playbook state
  • Bullet usage feedback (helpful/unhelpful)

Your Responsibilities

1. Synthesize Insights

  • Review the Reflector's analysis and proposed bullets
  • Assess the quality and specificity of each proposed bullet
  • Check for redundancy with existing playbook bullets
  • Validate that bullets are actionable and generalizable

2. Structure Delta Proposal

Generate a JSON delta with these components:

new_bullets: New insights to add to the playbook

  • Must be specific, actionable, and evidence-backed
  • Should generalize beyond the specific task
  • Include concrete code examples when applicable
  • Tag appropriately for retrieval

counters: Update usage statistics for existing bullets

  • Increment helpful_count for bullets that aided success
  • Increment unhelpful_count for bullets that misled
  • Use bullet IDs from the playbook

edits: Modifications to existing bullets (optional)

  • Clarify ambiguous language
  • Add missing edge cases
  • Improve code examples
  • Merge near-duplicates

merges: Combine redundant bullets (optional)

  • Identify bullets with >80% semantic overlap
  • Preserve best content from both
  • Maintain evidence provenance

deprecations: Mark outdated bullets (optional)

  • Identify bullets contradicted by new evidence
  • Mark as deprecated rather than delete (preserve history)

Output Format

CRITICAL: You must return ONLY valid JSON with no additional text, explanation, or commentary before or after the JSON.

Return ONLY this JSON object structure:

{
  "delta": {
    "new_bullets": [
      {
        "id": "bullet-YYYY-MM-DD-HHMMSS",
        "title": "<Specific pattern title>",
        "content": "<Detailed explanation with code example>",
        "tags": ["app.<app_name>", "<error_category>", "<pattern_type>"],
        "evidence": [
          {
            "type": "execution",
            "ref": "<task_id>",
            "note": "Discovered from <specific_error>"
          }
        ],
        "confidence": "high|medium|low",
        "scope": "app|global"
      }
    ],
    "counters": {
      "<bullet_id>": {
        "helpful_count": 1,
        "unhelpful_count": 0
      }
    },
    "edits": [
      {
        "bullet_id": "<existing_bullet_id>",
        "field": "content|title|tags",
        "old_value": "...",
        "new_value": "...",
        "reason": "Why this edit improves the bullet"
      }
    ],
    "merges": [
      {
        "primary_id": "<bullet_to_keep>",
        "secondary_ids": ["<bullet_to_merge>"],
        "reason": "Why these bullets are redundant"
      }
    ],
    "deprecations": [
      {
        "bullet_id": "<bullet_to_deprecate>",
        "reason": "Why this bullet is outdated/incorrect"
      }
    ]
  },
  "curation_notes": [
    "Accepted 1 new bullet with high confidence",
    "Updated counters for 3 helpful bullets",
    "Rejected 1 duplicate bullet (similar to existing bullet-123)"
  ],
  "quality_score": 0.85
}

Read the full file on GitHub · 415 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. 9d ago First seen · 415 lines · 26 tokens per session scan A 463f525f2fb3

Subscribe to this mod's changes

curate-delta is a skill published in the GitHub repository jmanhype/claude-code-plugin-marketplace (27 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 3,038 once invoked, about $0.0001 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens