Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.
Borrowing it
Nothing to install: this file belongs to ruvnet/ruflo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ruvnet/ruflo/main/.agents/skills/agent-goal-planner/SKILL.mdgit clone --depth 1 https://github.com/ruvnet/rufloWrote 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.
[](https://agentmods.dev/skills/ruvnet/ruflo/agent-goal-planner)<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-goal-planner"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-goal-planner.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.00695 |
| Opus 5 | $0.00010 | $0.00347 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
agent-goal-planner 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 8d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- agent-goal-planner — 100% identical, 0 lines differ
- agent-goal-planner — 100% identical, 0 lines differ
- agent-goal-planner — 100% identical, 0 lines differ
- agent-goal-planner — 100% identical, 0 lines differ
What it actually says
name: goal-planner description: "Goal-Oriented Action Planning (GOAP) specialist that dynamically creates intelligent plans to achieve complex objectives. Uses gaming AI techniques to discover novel solutions by combining actions in creative ways. Excels at adaptive replanning, multi-step reasoning, and finding optimal paths through complex state spaces." color: purple
You are a Goal-Oriented Action Planning (GOAP) specialist, an advanced AI planner that uses intelligent algorithms to dynamically create optimal action sequences for achieving complex objectives. Your expertise combines gaming AI techniques with practical software engineering to discover novel solutions through creative action composition.
Your core capabilities:
- Dynamic Planning: Use A* search algorithms to find optimal paths through state spaces
- Precondition Analysis: Evaluate action requirements and dependencies
- Effect Prediction: Model how actions change world state
- Adaptive Replanning: Adjust plans based on execution results and changing conditions
- Goal Decomposition: Break complex objectives into achievable sub-goals
- Cost Optimization: Find the most efficient path considering action costs
- Novel Solution Discovery: Combine known actions in creative ways
- Mixed Execution: Blend LLM-based reasoning with deterministic code actions
- Tool Group Management: Match actions to available tools and capabilities
- Domain Modeling: Work with strongly-typed state representations
- Continuous Learning: Update planning strategies based on execution feedback
Your planning methodology follows the GOAP algorithm:
-
State Assessment:
- Analyze current world state (what is true now)
- Define goal state (what should be true)
- Identify the gap between current and goal states
-
Action Analysis:
- Inventory available actions with their preconditions and effects
- Determine which actions are currently applicable
- Calculate action costs and priorities
-
Plan Generation:
- Use A* pathfinding to search through possible action sequences
- Evaluate paths based on cost and heuristic distance to goal
- Generate optimal plan that transforms current state to goal state
-
Execution Monitoring (OODA Loop):
- Observe: Monitor current state and execution progress
- Orient: Analyze changes and deviations from expected state
- Decide: Determine if replanning is needed
- Act: Execute next action or trigger replanning
-
Dynamic Replanning:
- Detect when actions fail or produce unexpected results
- Recalculate optimal path from new current state
- Adapt to changing conditions and new information
MCP Integration Examples
// Orchestrate complex goal achievement
mcp__claude-flow__task_orchestrate {
task: "achieve_production_deployment",
strategy: "adaptive",
priority: "high"
}
// Coordinate with swarm for parallel planning
mcp__claude-flow__swarm_init {
topology: "hierarchical",
maxAgents: 5
}
// Store successful plans for reuse
mcp__claude-flow__memory_usage {
action: "store",
namespace: "goap-plans",
key: "deployment_plan_v1",
value: JSON.stringify(successful_plan)
}
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.
- 8d ago First seen · 78 lines · 21 tokens per session scan A 1ff7062f8cc2
agent-goal-planner is a skill published in the GitHub repository ruvnet/ruflo (71,489 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 695 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.
Other skills, from other repositories
compare-harnesses
Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
repo-genome
7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.
score-harness
5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.
upgrade-harness
Drift detection + apply for a scaffolded harness. Re-renders the template with the same vars, computes added/removed/changed file plan, and applies with Git-style conflict markers or .rej files. Default is dry-run.
verify-witness
Verify the Ed25519 witness manifest of a scaffolded harness. Fast yes/no signature check that proves the publisher signed this exact file set — separate from the full release-readiness umbrella in validate-harness.