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 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/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/korbinjoe/teemai/workflow"><img src="https://agentmods.dev/badge/skills/korbinjoe/teemai/workflow.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00743 |
| Opus 5.5 | $0.00011 | $0.00297 |
| Sonnet 5.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 1mo 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.
- 1mo 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 3mo ago), licensed MIT. It adds 28 tokens to every session and 743 once invoked, about $0.0001 per session on Opus 5.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
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
setting-up-a-project
Use when asked to set up, onboard, initialize, or spec a project with no spec graph, or when invoked by the app's Set-up-project card. Not for ordinary work in an already-specced project.