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/pleaseai/claude-code-pluginsnpx agentmods add skills/pleaseai/claude-code-plugins/gws-workflowWrote 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/pleaseai/claude-code-plugins/gws-workflow)<a href="https://agentmods.dev/skills/pleaseai/claude-code-plugins/gws-workflow"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/gws-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/pleaseai/claude-code-plugins/gws-workflow"><img src="https://agentmods.dev/badge/skills/pleaseai/claude-code-plugins/gws-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.00013 | $0.00387 |
| Opus 5.5 | $0.00005 | $0.00155 |
| Sonnet 5.5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
gws-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.
This is a copy
100% identical to gws-workflow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
workflow (v1)
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws workflow <resource> <method> [flags]
Helper Commands
| Command | Description |
|---|---|
+standup-report |
Today's meetings + open tasks as a standup summary |
+meeting-prep |
Prepare for your next meeting: agenda, attendees, and linked docs |
+email-to-task |
Convert a Gmail message into a Google Tasks entry |
+weekly-digest |
Weekly summary: this week's meetings + unread email count |
+file-announce |
Announce a Drive file in a Chat space |
Discovering Commands
Before calling any API method, inspect it:
# Browse resources and methods
gws workflow --help
# Inspect a method's required params, types, and defaults
gws schema workflow.<resource>.<method>
Use gws schema output to build your --params and --json flags.
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 · 46 lines · 13 tokens per session scan A 17b209c8ed5e
gws-workflow is a skill published in the GitHub repository pleaseai/claude-code-plugins (16 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 387 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to gws-workflow, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
gsd-ns-manage
Invoke this Pi skill with /skill:gsd-ns-manage.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
to-spec
A process for turning the current conversation into a detailed feature specification and publishing it to the project’s issue tracker.
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…