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.
npx skills add MiaoDX/intuitive-flow --skill multica-goal-trackergit clone --depth 1 https://github.com/MiaoDX/intuitive-flowWrote 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/miaodx/intuitive-flow/multica-goal-tracker)<a href="https://agentmods.dev/skills/miaodx/intuitive-flow/multica-goal-tracker"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/multica-goal-tracker/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.
<a href="https://agentmods.dev/skills/miaodx/intuitive-flow/multica-goal-tracker"><img src="https://agentmods.dev/badge/skills/miaodx/intuitive-flow/multica-goal-tracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
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 16 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.
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.00086 | $0.01672 |
| Opus 5 | $0.00043 | $0.00836 |
| Sonnet 5 | $0.00017 | $0.00334 |
| Haiku 4.5 | $0.00009 | $0.00167 |
Grade A, and why
multica-goal-tracker 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.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multica Goal Tracker
Use this skill to keep Multica issues consistent when the human workflow is:
- Create or reuse a Multica issue.
- Paste the
/goalcommand that will drive a long$intuitive-flowor related skill run. - After the run completes, attach concise completion evidence.
- If the result is incomplete, keep the issue open and append the next goal as another attempt on the same issue.
- Repeat until the issue-level outcome is complete. Finish comments show the per-goal attempt plus cumulative issue time.
The skill can also create the Multica issue from an approved
$intuitive-preflight contract. That path records planning provenance and the
exact executable /goal, then immediately appends the normalized tracker start
comment. It does not execute the goal and does not create finish evidence.
Prefer appending comments over rewriting issue descriptions. Only update the description when the user explicitly wants the issue top-level description cleaned up.
All comments created by this skill use the current Multica user token, but they must begin with the visible marker:
> Agent 提交：以下内容由 Agent 帮忙整理并提交，用于和人工手写评论区分。
Keep this marker as the first visible line on start, finish, and final-review comments.
Create From Preflight
Use this after an $intuitive-preflight contract is approved and before the
goal is executed. The preflight must be DRAFT/approved, not
BLOCKED_NEEDS_DECISION, and it must contain either Main-session /goal prompt
or To execute with the executable /goal.
bun skills/multica-goal-tracker/scripts/track_goal.ts \
create-from-preflight \
--preflight-file /tmp/preflight.md \
--workspace-id product-workspace
Never rely on the Multica CLI default workspace when creating an issue from a
preflight. The default workspace may point at another product. If the user gives
a URL such as https://multica.example.test/product-workspace/, pass
--workspace-id product-workspace or the full URL so the script can resolve and verify
the real workspace id before writing.
What ships with it
8 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.
- agents/openai.yaml 225 B
- scripts/track_goal_attempts.ts 7.3 KB runs code
- scripts/track_goal_goal.ts 9.4 KB runs code
- scripts/track_goal_markdown.ts 8.3 KB runs code
- scripts/track_goal_multica.ts 8.3 KB runs code
- scripts/track_goal_session_evidence.ts 17 KB runs code
- scripts/track_goal.test.ts 34 KB runs code
- scripts/track_goal.ts 25 KB runs code
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.
- 9d ago First seen · 186 lines · 86 tokens per session scan A 6d2646e0a01a
multica-goal-tracker is a skill published in the GitHub repository MiaoDX/intuitive-flow (48 stars, last pushed 5d ago), licensed MIT. It adds 86 tokens to every session and 1,672 once invoked, about $0.0004 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
spawn-agent
Spawn worker agents (Gemini CLI or Codex CLI) to keep main context clean. Use for implementation, codebase research, context gathering, or any scoped work that would pollute the orchestrator's context.
track-creation
Create new Conductor tracks with spec, plan, and metadata files. Bundles all templates needed for track creation. Use when starting a new feature track via /omg:track or when manually creating tracks.
dev-updates
Detect and summarize uncommitted git changes grouped by feature area, then generate a structured commit message. Use when the user says "what's the update?", "what changed?", "summarize my changes", "what have I done?", or "what did I update?".
ticket-takeaway
Ticket Takeaway dashboard — track features from ideation to release. Generate visual dashboard, update item status in real-time, review completed features, add new items. Cross-project.
dashboard
Ticket Takeaway — track features from ideation to release. Generate visual dashboard, update item status in real-time, review completed features, add new items. Cross-project.
review
Review features in the For Review column — walk through tickets in batches, collect feedback or acceptance, create bug sub-tickets, and manage the acceptance flow.