Agent skill

Goal

by iurysza in iurysza/module-graph

Executes an approved goal package from ai-artifacts/goals. An agent skill from iurysza/module-graph.

MITAuto-check passed

Install Goal

skills CLI
$ npx skills add iurysza/module-graph --skill goal -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install iurysza/module-graph goal --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/iurysza/module-graph.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/goal .claude/skills/goal && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
goal
GitHub stars
420
Token cost
~721 tokens
SKILL.md length
385 words
Files
1
Skills in repo
16
Repo updated
First seen
Licence
MIT

At a glance

Executes an approved goal package from ai-artifacts/goals. An agent skill from iurysza/module-graph.

  • Works in 6 steps: Read repository instructions first. → Require an explicit goal.md path from… → Read goal.md and resolve its links… → …
  • The user provides a goal.md path
  • SKILL.md covers Load the contract, Execute, Delegation and Finish
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Goal is an agent skill from iurysza/module-graph. Executes an approved goal package from ai-artifacts/goals. Use when the user provides a goal.md path or asks to implement a goal created by setup-goal.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A Gradle Plugin for visualizing your project's structure, powered by mermaidjs. The licence is MIT.

When your agent uses it

  • The user provides a goal.md path
  • Asks to implement a goal created by setup-goal

Example prompts

  • “Use the goal skill to execute an approved goal package from ai-artifacts/goals. An agent skill from iurysza/module-graph”
  • “/goal”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Read repository instructions first.
  2. Require an explicit goal.md path from the user. Do not guess the latest or nearest package.
  3. Read goal.md and resolve its links relative to the package directory.
  4. Require and read facts.md, facts.meta.json, plan.md, and dev-log.md.
  5. Read intent.md when the package contains or links it. Older approved packages without intent.md remain valid.
  6. Stop if a required file is missing, a link is broken, fact metadata does not match the accepted facts, or a product, scope, architecture…

What it can do on your machine

Read from SKILL.md and the folder at commit 15b0135. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Goal loads about 721 tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 385 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~39
When it runs · the whole SKILL.md, loaded when a task matches
~721

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iurysza/module-graph at commit 15b0135, republished under its MIT licence (© iurysza). 385 words, ~721 tokens.

Download SKILL.mdSave it as .claude/skills/goal/SKILL.md (or your agent's skills folder).
name
goal
description
Executes an approved goal package from ai-artifacts/goals. Use when the user provides a goal.md path or asks to implement a goal created by setup-goal.
metadata.category
planning-architecture

Execute Goal

Execute an approved package at ai-artifacts/goals/<slug>/goal.md. Invoking this skill with a package is approval to begin implementation; it is not permission to rediscover scope or rewrite the contract.

Load the contract

  1. Read repository instructions first.
  2. Require an explicit goal.md path from the user. Do not guess the latest or nearest package.
  3. Read goal.md and resolve its links relative to the package directory.
  4. Require and read facts.md, facts.meta.json, plan.md, and dev-log.md.
  5. Read intent.md when the package contains or links it. Older approved packages without intent.md remain valid.
  6. Stop if a required file is missing, a link is broken, fact metadata does not match the accepted facts, or a product, scope, architecture, security, or destructive decision remains unresolved.

Accepted facts are the implementation contract. Do not edit intent.md when present, facts.md, or facts.meta.json during execution. Do not revise plan.md unless the user explicitly sends the package back to setup or replanning.

Execute

  1. Briefly state the goal, approved scope, and execution approach.
  2. Follow the approved plan in order. Use the narrowest implementation that satisfies every accepted fact.
  3. Preserve unrelated work. Keep one writer per worktree unless parallel work is deliberately isolated.
  4. Append concise entries to dev-log.md: completed work, changed files, validation, blockers, and remaining work. Never rewrite prior entries or claim work not performed.
  5. Run every verification required by plan.md.
  6. For each fact whose automatedVerification is true, run or add a concrete automated check. Record a blocker instead of pretending a check passed.
  7. Record manual evidence for facts that cannot be verified automatically.
Show full SKILL.md (120 more words)Show less

If implementation exposes a new material decision or contradicts an accepted fact, stop and ask the user. Do not silently expand scope or mutate the contract.

Delegation

Delegate only when the host supports it and the role is directly useful. Every delegated task must name the exact goal.md path and instruct the worker to load the package. Never ask another agent to infer which goal applies.

Use isolated worktrees for parallel writers. Read-only research and review may run in parallel without sharing write ownership.

Finish

Before declaring completion, compare the implementation and evidence against every accepted fact and the done condition in goal.md.

Report:

  • implemented behavior;
  • changed files;
  • checks run and outcomes;
  • manual verification;
  • blockers or remaining work;
  • dev-log.md path.

© iurysza, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/goal of iurysza/module-graph.

Open the folder on GitHubat commit 15b0135

Compare with similar skills

Goal next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Goal compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Goal this skilliurysza/module-graph420—~721Automated safety check: PassMIT
Executealirezarezvani/claude-skills28k—~831Automated safety check: PassMIT
Goalscodewhale-hq/Codewhale41k—~273Automated safety check: PassMIT
Artifacts Buildernexu-io/open-design100k—~347Automated safety check: PassApache-2.0
Debugging Executionsn8n-io/n8n207k—~2.6kAutomated safety check: PassCustom licence
Web Artifacts Builderanthropics/skills180k41 repos~769Automated safety check: PassApache-2.0

Similar skills

  • Execute

    alirezarezvani/claude-skills

    /cs:execute <decision — Generate a 90-day execution plan with weekly milestones, DRIs, and check-in cadence from an approved decision.

    28k GitHub stars~831 tokensUpdated 1 mo ago
    Product & Project ManagementAuto-check passed
  • Goals

    codewhale-hq/Codewhale

    Set, review, and update the user's goals. An agent skill from codewhale-hq/Codewhale.

    41k GitHub stars~273 tokensUpdated today
    Auto-check passed
  • Artifacts Builder

    nexu-io/open-design

    Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui).

    100k GitHub stars~347 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Official

    Debug failed or wrong-output workflow executions using executions tools.

    207k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed
  • Web Artifacts Builder

    anthropics/skills

    Official

    Builds multi-component claude.ai HTML artifacts as a small React, TypeScript and Tailwind project, then bundles it into one shareable HTML file.

    180k GitHub starsUsed in 41 repos~769 tokens
    Frontend & DesignAuto-check passed
  • Goal Plan

    ruvnet/ruflo

    Create and execute Goal-Oriented Action Plans (GOAP) with precondition analysis, cost optimization, and adaptive replanning

    74k GitHub stars~807 tokensUpdated today
    Auto-check: notes

More from iurysza/module-graph

All 16 skills in this repo
  • Audio Transcribe

    iurysza/module-graph

    Transcribes local audio into Markdown with Gemini 3.5 Transcribe, including speaker labels and provider timestamps.

    420 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Chatgpt Imagegen

    iurysza/module-graph

    Generates or edits raster images through OpenAI's Image API.

    420 GitHub stars~726 tokensUpdated yesterday
    Auto-check passed
  • Gemini Tts

    iurysza/module-graph

    Generates spoken MP3 audio from text or Markdown with Gemini TTS.

    420 GitHub stars~968 tokensUpdated yesterday
    Auto-check passed
  • Skill Cleaner

    iurysza/module-graph

    Audits installed Agent Skills for duplicates, unused candidates, loaded roots, oversized descriptions, and prompt cost.

    420 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed
  • Brainstorming

    iurysza/module-graph

    Explores and validates a feature, component, workflow, or behavior change before implementation.

    420 GitHub stars~723 tokensUpdated yesterday
    Auto-check passed
  • Domain Modeling

    iurysza/module-graph

    Maintains project domain language, context maps, diagrams, and architectural decisions under ai-artifacts.

    420 GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

Questions about Goal

What does Goal do?

Executes an approved goal package from ai-artifacts/goals. An agent skill from iurysza/module-graph. Goal is an agent skill from iurysza/module-graph. Executes an approved goal package from ai-artifacts/goals.

When should I use Goal?

Goal fits situations like: the user provides a goal.md path; asks to implement a goal created by setup-goal.

How do I install Goal in Claude Code?

Run `npx skills add iurysza/module-graph --skill goal -a claude-code`. Or copy the skill folder (.agents/skills/goal in iurysza/module-graph) into .claude/skills/goal in your project. Claude Code loads it when a task matches its description.

How do I install Goal in Codex?

Run `npx skills add iurysza/module-graph --skill goal -a codex`. Or copy the skill folder (.agents/skills/goal in iurysza/module-graph) into .agents/skills/goal in your project. Codex loads it when a task matches its description.

Can I use Goal in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iurysza/module-graph --skill goal -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/goal, .gemini/skills/goal, .github/skills/goal and .opencode/skills/goal in your project.

What does Goal need to run?

SKILL.md names no scripts, command-line tools or credentials: Goal is instructions for the agent only.

Does Goal access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Goal safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Goal use?

Goal is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Goal use?

About 721 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Goal?

Skills that share tags, products or a category with Goal: Execute (alirezarezvani/claude-skills, 28k stars), Goals (codewhale-hq/Codewhale, 41k stars), Artifacts Builder (nexu-io/open-design, 100k stars) and Debugging Executions (n8n-io/n8n, 207k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Goal?

iurysza (a GitHub user) maintains it in iurysza/module-graph, which has 420 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 8, 2026.

Source: iurysza/module-graph on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.