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 dryvist/claude-code-plugins --skill workspace-standardsgit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/workspace-standards)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/workspace-standards"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/workspace-standards/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/dryvist/claude-code-plugins/workspace-standards"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/workspace-standards.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.00016 | $0.00360 |
| Opus 5.5 | $0.00006 | $0.00144 |
| Sonnet 5.5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
workspace-standards 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
Workspace Management Standards
Cross-Project Documentation
Each project must maintain:
- README.md at root: purpose, quick start, usage examples, cost implications
- Directory structure docs for complex projects
- Change logs for significant modifications
Git Workflow
- Branching:
mainfor production. Prefixes:feature/,bugfix/,hotfix/,release/,chore/. - Commits: Follow Conventional Commits (
feat:,fix:,docs:, etc.). - Worktrees: All development in dedicated worktrees
(see
/git-workflow-standards).
Security
- Use
.envlocally (never committed) and secure parameter stores for cloud. - Principle of least privilege for all resources and services.
Cost Management
| Environment | Lifecycle |
|---|---|
| Development | Automated shutdown |
| Testing | Manual cleanup |
| Production | Scheduled backups |
Define and monitor monthly budgets per environment.
Project Lifecycle
- Create: Initialize with standard templates (README, .gitignore, LICENSE).
- Maintain: Review dependencies, update docs, optimize costs.
- Retire: Document, archive, clean up.
Related Skills
- claude-skill-authoring (project-standards) — Use when authoring Claude skills/agents/rules — token budgets, progressive disclosure, placement
- skills-registry (project-standards) — Use when looking up available tools, skills, commands, agents, or plugins
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 · 49 lines · 16 tokens per session scan A dd36f2f23383
workspace-standards is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 16 tokens to every session and 360 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-09-04.
Other skills, from other repositories
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
claim
Acquire, renew or release a Fakoli State task lease when beginning work or recovering an interrupted claim.
omh-github-issue-intake
This is an OMH github-issue-intake workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.