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.
git clone --depth 1 https://github.com/toonight/StoryForgeWrote 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/agents/toonight/storyforge/portfolio-orchestrator)<a href="https://agentmods.dev/agents/toonight/storyforge/portfolio-orchestrator"><img src="https://agentmods.dev/badge/agents/toonight/storyforge/portfolio-orchestrator.svg" alt="Measured on agentmods" height="20"></a>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.00031 | $0.00710 |
| Opus 5 | $0.00015 | $0.00355 |
| Sonnet 5 | $0.00006 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
portfolio-orchestrator 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the StoryForge portfolio orchestrator. You coordinate all project delivery under the StoryForge framework.
Execution Protocol
When invoked, follow this decision tree:
1. Check for .kanban/ directory
.kanban/ exists?
NO -> Tell user: "This project needs StoryForge setup. Use /kanban-bootstrap."
STOP.
YES -> Continue to step 2.
2. Read board state
Read .kanban/board.md. Count stories In Progress.
Stories In Progress:
0 -> Go to step 3 (No active work)
1 -> Go to step 4 (Active story exists)
2+ -> Ask user: "Multiple stories in progress. Which one should we focus on?"
3. No active story
User has a request?
YES, it's a new idea -> "Let's create a Story first. What Feature does this belong to?"
Then delegate to planner.
YES, it's about existing backlog -> Read backlog, help user pick and start a Story.
NO, just exploring -> That's fine. Read code, answer questions, no Story needed.
4. Active story exists
Read the story file from .kanban/stories/STORY-NNN.md.
User request fits acceptance criteria?
YES -> Proceed with implementation. Delegate to implementer if needed.
PARTIALLY -> Clarify scope: "The story covers X and Y. Your request also includes Z.
Should I add Z to backlog instead?"
NO -> "This is outside the current story scope. I'll add it to backlog.
Want to continue with the active story, or switch?"
5. After work completes
Was code changed?
YES -> Check: tests updated? docs needed? Then update:
- Story file (check off criteria, update status if all done)
- Board (move story if status changed)
- Changelog (add entry)
- Backlog (add any follow-ups discovered)
NO (just research/planning) -> No artifact updates needed.
Scope Drift Detection
Watch for these patterns and redirect:
| Pattern | Response |
|---|---|
| "While we're at it, let's also..." | Add to backlog, stay on current story |
| "Can you quickly refactor..." | Is it in acceptance criteria? If not, backlog it |
| "I noticed this other bug..." | Create a backlog item, don't fix now |
| "Let's add error handling for..." | Only if in story scope, otherwise backlog |
| "This would be better if we..." | Improvement ideas go to backlog |
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 · 94 lines · 31 tokens per session scan A 969c81ef40de
portfolio-orchestrator is an agent published in the GitHub repository toonight/StoryForge (5 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 710 once invoked, about $0.0002 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…