ultragoal

ultragoal is a skill for Claude Code from Yeachan-Heo/gajae-code. It costs 22 tokens per session (12,645 once invoked), scanned A, original, MIT.

A workflow for creating and completing durable, multi-goal plans stored as files in a repository. It uses goals.json for goal state and ledger.jsonl for checkpoints, evidence, blockers, and reviews.

In plain words
What is it for?
It helps create several related goals, execute them in sequence, record receipts and decisions, handle blockers, and verify completion from durable artifacts.
Why use it?
It keeps long-running work and its proof in repository files, so progress can be checked even after an interactive session ends.

Skill for Claude Code

Written for Claude Code: UserPromptSubmit hook event. Also seen: mentions subagents.

Good fit It helps create several related goals, execute them in sequence, record receipts and decisions, handle blockers, and verify completion from durable artifacts.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yeachan-heo/gajae-code/ultragoal
About the project

Gajae Code is an external coding-agent harness that works inside repositories or worktrees and guides an agent through planning, review, approval, and code changes. It is for developers who want to use an existing coding-plan subscription while controlling agent work from a terminal, phone, or bot. The catalogue entries provide extensions such as skills, agents, commands, plugins, and MCP integrations for the harness.

Yeachan-Heo/gajae-code · 2,752 stars · on GitHub

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 Yeachan-Heo/gajae-code --skill ultragoal
Clone the repo
git clone --depth 1 https://github.com/Yeachan-Heo/gajae-code

Made for: Claude Code.

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 ultragoal

README.md
[![agentmods](https://agentmods.dev/badge/skills/yeachan-heo/gajae-code/ultragoal/github.svg)](https://agentmods.dev/skills/yeachan-heo/gajae-code/ultragoal)
Your own site
<a href="https://agentmods.dev/skills/yeachan-heo/gajae-code/ultragoal"><img src="https://agentmods.dev/badge/skills/yeachan-heo/gajae-code/ultragoal/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 ultragoal

Your own site · 80×15
<a href="https://agentmods.dev/skills/yeachan-heo/gajae-code/ultragoal"><img src="https://agentmods.dev/badge/skills/yeachan-heo/gajae-code/ultragoal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 12,645 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Rogue Agent · line 3
    Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
    Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00022 $0.12645
Opus 5 $0.00011 $0.06323
Sonnet 5 $0.00004 $0.02529
Haiku 4.5 $0.00002 $0.01264

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

Security

Grade A, and why

ultragoal 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 yesterday.

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.

packages/coding-agent/src/defaults/gjc/skills/ultragoal/SKILL.md · 488 lines

How it starts

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

Ultragoal Workflow

Use when the user asks for ultragoal, create-goals, complete-goals, durable multi-goal planning, or sequential execution over GJC goal mode.

Purpose

ultragoal turns a brief into repo-native durable artifacts and then drives execution through the unified goal tool as a UX bridge only. goals.json is the canonical source of goal identity and state; ledger.jsonl is the canonical proof stream for checkpoints, receipts, blockers, steering, and reviews. The inline goal tool and goal-mode-request create-bridge exist only to keep the agent's interactive loop focused on the current aggregate or story objective. Completion is verified purely from durable goals.json plus fresh ledger.jsonl receipts, never from inline goal state. The agent, not the CLI or hooks, calls goal({"op":"complete"}) or goal({"op":"drop"}) after durable run completion or cleanup; CLI commands and hooks never mutate goal state.

  • .gjc/_session-{sessionid}/ultragoal/brief.md
  • .gjc/_session-{sessionid}/ultragoal/goals.json
  • .gjc/_session-{sessionid}/ultragoal/ledger.jsonl (checkpoint and structured steering audit events)

Existing aggregate plans with the legacy enumerated objective are migrated to the stable pointer objective on read, persisted to goals.json, retained in gjcObjectiveAliases for already-active hidden goal reconciliation, and audited with an aggregate_objective_migrated ledger entry.

  • Nudge budget setting — the per-story give-up budget (gjc.ultragoal.nudgeBudget, default 10, non-negative integer) is read through one shared resolver in this exact order (first valid value wins):
    1. project .gjc/config.yml
    2. user <agentDir>/config.yml (normally ~/.gjc/agent/config.yml, honoring GJC_CODING_AGENT_DIR/PI_CODING_AGENT_DIR; XDG applies only to categorized data/state/cache subdirs, never the workflow config path)
    3. built-in default config.yml uses the nested (schema) form - gjc: { ultragoal: { nudgeBudget } }. Project configuration beats user configuration. The reported source is the canonical path of the winning file, or default. config.yml is the ONLY settings surface: the legacy settings.json files (project and config-root) are retired: the config-root ~/.gjc/settings.json is migrated once into the default global agent config.yml and its source removed, while the project .gjc/settings.json is retained for non-workflow settings (only its workflow keys are migrated into project .gjc/config.yml and no longer read unless a migration target is absent - a migration that could not publish (e.g. a read-only .gjc) leaves the retained legacy value effective as the previously configured override until it can publish). Invalid optional settings files continue to the next layer or the default (tolerant).

Read the full file on GitHub · 488 lines

Files

What ships with it

2 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. yesterday Changed · +22 lines dc1c4edb785a
  2. 10d ago First seen · 466 lines · 22 tokens per session scan A a68c2b6aabf5

Subscribe to this mod's changes

ultragoal is a skill published in the GitHub repository Yeachan-Heo/gajae-code (2,752 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 12,645 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