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/openase-platformWrote 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/openase-platform)<a href="https://agentmods.dev/skills/pacificstudio/openase/openase-platform"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/openase-platform/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/openase-platform"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/openase-platform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Memory Poisoning · line 105 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
- medium Agent Snooping · line 516 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00018 | $0.05975 |
| Opus 5.5 | $0.00007 | $0.02390 |
| Sonnet 5.5 | $0.00004 | $0.01195 |
| Haiku 4.5 | $0.00002 | $0.00598 |
Grade A, and why
openase-platform 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 — 743 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenASE Platform Operations
Prefer the wrapper injected into the workspace:
./.openase/bin/openase ticket list --status-name Todo
This wrapper is the openase binary with the current workspace's OpenASE
platform context already attached. Use it first. Do not hand-roll URLs, guess
endpoints, bypass the platform by writing the database directly, or fake
platform state.
Core Concepts
Use these distinctions before you choose commands or explain the platform to a user:
workflow: the execution policy for a role. A workflow decides which agent handles work, which ticket statuses it may pick up, which statuses count as finished, which harness instructions and skills are active, and which platform scopes the runtime may use.updates: curated project progress threads for humans. Use these for milestone checkpoints, risk reporting, stakeholder communication, and discussion. Updates are intentionally higher-signal than raw runtime logs.activity: the append-only project event stream. It records what actually happened across tickets, agents, workflows, and platform writes for traceability, debugging, and auditability.
One short mental model:
- workflows decide how work runs
- activity records what happened
- updates summarize what matters
Keep the boundaries clear:
- Do not describe
workflowas "just a prompt"; it is prompt + routing + policy + execution limits. - Do not treat
updatesas a synonym foractivity; updates are curated, while activity is the raw event timeline. - Do not treat
activityas a task board; it explains history, not desired future state.
What This Skill Is For
OpenASE is not a small helper that just runs commands. It is an issue-driven automated software engineering platform. Per the PRD, it is responsible for at least:
- Project control: descriptions, statuses, repos, workflows, skills, and scheduled jobs
- Ticket control: lifecycle, status transitions, comment primitives, usage/cost, and external links
- Execution control: agents, providers, machines, runtimes, and orchestration loops
- Controlled autonomy: agents can operate the platform within granted scope and close the loop from claim to execution to platform writeback to follow-up tickets
- Auditability: every platform write goes through the API / ActivityEvent / timeline and stays attributable
What ships with it
1 file 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 · 743 lines · 18 tokens per session scan A cf90e8aff8e6
openase-platform is a skill published in the GitHub repository PacificStudio/openase (269 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 5,975 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
wework-notifications
Send Wework in-app notifications when a user requests an alert, greeting, or automation notification. Works in ordinary conversations without a project or board, with optional project links and delivery to connected IM sessions.
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
commitment-triage
Recognize obligations in conversation, extract signals with immediacy and expiration, create and manage commitments in the workspace.
notion
Read and write Notion — search pages/databases, query a database, create pages, append blocks — via the official Notion REST API and the user's own integration token. Use when asked to "add to Notion", "find in my Notion", "create a Notion page", "update my Notion database".
lark-workflow-standup-report
A workflow that combines calendar events with unfinished Lark tasks to produce a daily or weekly work summary.
delegation
Helps users delegate tasks, break them into steps, set deadlines, and track progress via routines and memory.