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 PacificStudio/openase --skill workflow-authoringgit clone --depth 1 https://github.com/PacificStudio/openaseWrote 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/pacificstudio/openase/workflow-authoring)<a href="https://agentmods.dev/skills/pacificstudio/openase/workflow-authoring"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/workflow-authoring/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/pacificstudio/openase/workflow-authoring"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/workflow-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02593 |
| Opus 5.5 | $0.00011 | $0.01037 |
| Sonnet 5.5 | $0.00006 | $0.00519 |
| Haiku 4.5 | $0.00003 | $0.00259 |
Grade A, and why
workflow-authoring 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Authoring
Overview
Use this skill when creating or editing an OpenASE workflow harness file. Its job is to turn a vague workflow idea into a concrete harness that clearly defines what the workflow owns, what counts as completion, how ticket state should move, where feedback comes from, and how work survives beyond a disposable ticket workspace.
This skill is about authoring the workflow file itself, not just the underlying engineering task.
Runtime Reality You Must Design Around
OpenASE ticket execution is not a persistent personal development environment.
- Each ticket run gets its own workspace.
- That workspace is created when the ticket starts running.
- The local contents of that ticket workspace are disposable and may be cleaned up after the run finishes.
- Any output that must survive the run must be pushed to the repository or written back to durable OpenASE surfaces such as ticket comments or project updates.
A good workflow harness must make that lifecycle explicit. Do not write harnesses that assume a long-lived local scratchpad or future manual cleanup inside the same workspace.
Use The Shared Platform Contract
Remember that every workflow already receives shared workflow execution rules from the platform. Reuse and specialize those rules instead of fighting them.
In particular, author around these always-on assumptions:
- ticket comments are the durable output channel
- the current workflow pickup status is the active owned lane
- the current workflow finish status must only be used when the workflow deliverable is truly ready
- blocked termination must be reserved for genuinely unprogressable cases
- interactive waiting is not a reliable operating model
Write harness content that sharpens these generic rules for one workflow rather than duplicating all of them verbatim.
What Every Workflow File Must Define
At minimum, a workflow harness should make these items explicit:
- The workflow's primary mission.
- What class of tickets this workflow is for.
- What it is expected to deliver.
- What it must not take on.
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 · 327 lines · 28 tokens per session scan A 4e673ff908a5
workflow-authoring is a skill published in the GitHub repository PacificStudio/openase (269 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,593 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-30.
Other skills, from other repositories
aisee:init
A project setup and audit helper for OpenSpec, a system for planning and tracking software changes, in Aisee projects.
aisee:srs
A structured conversation and documentation tool for creating a software requirements specification, or SRS. An SRS records users, goals, scope, workflows, rules, permissions, exceptions, and acceptance needs before technical design or coding.
aisee:change-author
A document-writing tool for one already-approved OpenSpec change. OpenSpec is a way to describe software changes in structured documents before implementation.
aisee:change-plan
A planning tool that turns an approved software request or project fact into one or more clearly separated OpenSpec changes. OpenSpec is a structured way to plan and describe software work before implementation.
aisee:image-object
A workflow for extracting reusable objects from an existing image, such as a product or person, and saving cutouts, masks, repaired backgrounds, and image variants. A mask is a shape that marks which pixels belong to the selected object.
aisee:reflect
A guide for reviewing a work session and saving reusable lessons as project documents. It distinguishes temporary suggestions from confirmed long-term team knowledge and from records of specific solved problems.