Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/PacificStudio/openasenpx agentmods add skills/pacificstudio/openase/ticket-workpadWrote 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/ticket-workpad)<a href="https://agentmods.dev/skills/pacificstudio/openase/ticket-workpad"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/ticket-workpad/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/ticket-workpad"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/ticket-workpad.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.00023 | $0.00603 |
| Opus 5.5 | $0.00009 | $0.00241 |
| Sonnet 5.5 | $0.00005 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
ticket-workpad 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.
What it actually says
Ticket Workpad
The Workpad is the single persistent progress board for the current ticket. Bind this skill to ticket workflows that need long-running execution and resume support so agents consistently write durable state into one persistent comment instead of scattering it across ephemeral context.
Its job is not to expose platform APIs directly. It defines a persistence convention on top of primitive platform comments:
- The platform base comes from the
openase-platformskill:ticket comment list/create/update. ticket-workpaddefines which comment counts as the workpad, how to upsert it idempotently, and which sections should be maintained.- This lets later agents recover execution state from the same workpad comment even after runtime restarts, rescheduling, or lost conversation context.
Workpad upsert is no longer a standalone CLI subcommand. Call the injected openase-platform helper script instead; it will add the standard heading automatically and reuse or update the persistent comment.
Recommended usage:
cat <<'EOF' >/tmp/workpad.md
Environment
- <host>:<abs-workdir>@<short-sha>
Plan
- step 1
- step 2
Progress
- inspecting current implementation
Validation
- not run yet
Notes
- assumptions or blockers
EOF
OPENASE_PLATFORM_HELPER=""
for candidate in \
./.codex/skills/openase-platform/scripts/upsert_workpad.sh \
./.claude/skills/openase-platform/scripts/upsert_workpad.sh \
./.gemini/skills/openase-platform/scripts/upsert_workpad.sh \
./.agents/skills/openase-platform/scripts/upsert_workpad.sh \
./.agent/skills/openase-platform/scripts/upsert_workpad.sh
do
if [ -x "$candidate" ]; then
OPENASE_PLATFORM_HELPER="$candidate"
break
fi
done
if [ -z "$OPENASE_PLATFORM_HELPER" ]; then
echo "openase-platform helper script not found" >&2
exit 1
fi
"$OPENASE_PLATFORM_HELPER" --body-file /tmp/workpad.md
Execution rules:
- Write the first workpad before you start changing code. Do not backfill it afterward.
- Update the same comment after each major phase instead of creating new comments repeatedly.
- Continuously maintain at least
Plan,Progress,Validation, andNotes. - Treat the workpad as the resume point across runtimes and record the information the next agent will actually need, not a one-off chat summary.
- If the workflow binds this skill, maintaining the workpad is mandatory. It is part of the execution loop, not optional decoration.
- If you are blocked, record the blocker and missing prerequisites in the workpad instead of exiting silently.
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 · 69 lines · 23 tokens per session scan A 37459d8b7834
ticket-workpad is a skill published in the GitHub repository PacificStudio/openase (269 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 603 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.
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
omh-research-department
This is a Hermes-native research-department workflow skill.
omh-agent-board
This is a Hermes-native agent-board workflow skill.
company-employee
The protocol every employee of a PenguinHarness organization follows — read the handbook first, act on [orgtrigger] work runs, schedule tickets from the desk session and do the work in ticket sessions, block instead of idling, ask the board in the all-hands channel before anything heavy, costly, irreversible or…
company-ceo
Run a PenguinHarness organization as its CEO — turn the mission into a ticket tree, hire HR and finance first, partition the shared workspace, schedule the calendar, open a channel per stream, review tickets and report to the board in the all-hands channel.