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 agentmods add skills/codeinfinity1/stram/taskflownpx skills add CodeInfinity1/Stram --skill taskflowgit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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 | $0.00028 | $0.00600 |
| Opus 5 | $0.00014 | $0.00300 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
taskflow 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TaskFlow
Tool Map
cognitive_goal_createcognitive_commitment_recordcognitive_commitment_updatecognitive_wakeup_schedulecognitive_trigger_recordautonomous_task_graph_createautonomous_queue_statusautonomous_cycle_runmulti_agent_coordinatemulti_agent_board
Use this skill when work should outlive one prompt, wait on external events, delegate subtasks, or require resumable progress.
When To Use
- Multi-step tasks with one owner.
- Work that needs scheduled follow-up.
- Work waiting on a person, channel reply, file change, or external system.
- Background tasks that need status, cancellation, or resumption.
- Delegated coding or research jobs with child tasks.
Stram Shape
Use cognitive tools and stores for:
- goals;
- tasks;
- wakeups;
- triggers;
- runtime event queue;
- autonomous cycles;
- memories and learning records.
Workflow
- Create or reuse an active goal.
- Add tasks with success criteria.
- For work that cannot continue now, schedule a wakeup or trigger.
- For background progress, run an autonomous cycle.
- For delegation, link the child run or worker result back to the goal/task.
- On completion, record evidence and learning.
Wait States
Use a waiting state when:
- credentials are missing;
- approval is required;
- a user reply is needed;
- a remote channel must deliver a response;
- a scheduled time has not arrived.
Record the reason and the exact next stimulus that should resume the work.
Verification
- Every durable task should have an owner, status, reason, and evidence refs.
- Do not create background loops without a stopping condition.
- Do not mark a task complete merely because a run started.
Safety And Approval
- Durable goals, commitments, wakeups, triggers, and delegated tasks should be created only when they represent real user intent or model-supported task state.
- Do not schedule external-visible actions, live sends, installs, deploys, or destructive work without explicit approval.
- Keep waiting states honest: name the exact blocker, owner, and resume stimulus.
- Do not mark a task complete until evidence proves the requested end state, not merely a plan, queued run, or worker handoff.
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.
- yesterday First seen · 82 lines · 28 tokens per session scan A ccaccc25b4a0
taskflow is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 600 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.