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/korbinjoe/teemai/workflownpx skills add korbinjoe/TeemAI --skill workflowgit clone --depth 1 https://github.com/korbinjoe/TeemAIWrote 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/korbinjoe/teemai/workflow)<a href="https://agentmods.dev/skills/korbinjoe/teemai/workflow"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/workflow.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 | $0.00028 | $0.00743 |
| Opus 5 | $0.00014 | $0.00371 |
| Sonnet 5 | $0.00006 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
workflow 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 3d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow DAG
For tasks with multiple steps and dependencies, submit a DAG to the server. The server-side WorkflowEngine handles scheduling, agent startup, failure policies, and completion notification. Exit immediately after submission.
Environment Variables (Injected)
| Variable | Description |
|---|---|
AGENT_API_BASE |
teemai-server HTTP address |
TEEMAI_CHAT_ID |
Current chat ID |
TEEMAI_INSTANCE_ID |
Your instance ID |
Create Workflow
bash {SKILL_DIR}/scripts/create-workflow.sh '<dag-json>'
DAG JSON format:
{
"tasks": [
{ "taskId": "t1", "agentId": "fullstack-engineer", "description": "Implement feature", "dependsOn": [], "onFailure": "stop" },
{ "taskId": "t2", "agentId": "code-reviewer", "description": "Review implementation", "dependsOn": ["t1"], "onFailure": "stop" }
]
}
Task fields:
taskId: unique identifier within the workflowagentId: which expert agent to run this taskdescription: task description sent to the agentdependsOn: array of taskIds that must complete firstonFailure:stop(halt DAG),skip(continue others),retry(re-run)maxRetries: retry attempts (default 1, only forretrypolicy)maxRejects: max times Lead can reject this task (default 2)timeoutMinutes: per-task timeout (default 30)
List Workflows
bash {SKILL_DIR}/scripts/list-workflows.sh [status]
Filter by status: running, suspended, completed, stopped
Resume Workflow
bash {SKILL_DIR}/scripts/resume-workflow.sh <workflow-id>
Advance Workflow
bash {SKILL_DIR}/scripts/advance-workflow.sh '<workflow-id>'
Start all ready tasks in a workflow. Called by Lead after receiving a
[Workflow progress] notification and reviewing the completed task.
Reject Task
bash {SKILL_DIR}/scripts/reject-task.sh '<workflow-id>' '<task-id>' '<feedback>'
Reject a completed task and send it back for rework with feedback. The task
resets to pending and restarts with the feedback prepended to the agent's
prompt. Each task can be rejected up to maxRejects times (default 2).
What ships with it
2 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.
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.
- 3d ago First seen · 102 lines · 28 tokens per session scan A 2229e40bd394
workflow is a skill published in the GitHub repository korbinjoe/TeemAI (2 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 743 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
agent-spec-tool-first
CRITICAL: Use for agent-spec CLI tool workflow. Triggers on: agent-spec, contract, lifecycle, guard, verify, explain, stamp, checkpoint, plan, requirements, work-units, knowledge requirements, KLL, docs vs knowledge, spec verification, task contract, spec quality, lint spec, run log, "how to verify", "how to use…
importing-a-codebase
Use when the repo holds real source code but no specs: the existing-codebase branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for empty workspaces (starting-a-new-project) or feature work in a specced project (brainstorming).
starting-a-new-project
Use when the workspace is empty — no code yet — and the user brings a raw idea: the brand-new branch of setting-up-a-project, normally reached via that dispatcher, directly only when the situation is unmistakable. Not for features in an existing project — use brainstorming instead.
agent-spec-authoring
CRITICAL: Use for writing and editing agent-spec .spec/.spec.md files. Triggers on: write spec, create spec, edit spec, new spec, spec authoring, task contract, .spec file, .spec.md file, BDD scenario, acceptance criteria, completion criteria, test selector, boundary, constraint, intent, decision, out of scope, "how…
agent-spec-estimate
CRITICAL: Use for estimating work effort from agent-spec Task Contracts. Triggers on: estimate, estimation, how long, work effort, round count, time estimate, scope, sizing, cost, budget, planning, sprint, capacity, "how many rounds", "how long will this take", "estimate this spec", 估算, 工作量, 多久, 时间估算, 预估, 工时, 规模…
agent-spec-intent-compiler
Use when converting PRD or issue prose into KLL requirements, running the intent compiler plan, or reverse-interviewing a human to resolve requirement ambiguity before task spec generation.