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 forcedotcom/sf-skills --skill dx-devops-project-managegit clone --depth 1 https://github.com/forcedotcom/sf-skillsWrote 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/forcedotcom/sf-skills/dx-devops-project-manage)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/dx-devops-project-manage"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/dx-devops-project-manage/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/forcedotcom/sf-skills/dx-devops-project-manage"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/dx-devops-project-manage.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.00186 | $0.03207 |
| Opus 5 | $0.00093 | $0.01604 |
| Sonnet 5 | $0.00037 | $0.00641 |
| Haiku 4.5 | $0.00019 | $0.00321 |
Grade A, and why
dx-devops-project-manage 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 7d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Center Project Management
Manages the complete DevOps Center project lifecycle — from listing existing projects through creation to updating project settings. Provides headless CLI-driven operations for autonomous release workflows.
Scope
- In scope: List DevOps Center projects, create a new project, update project fields (name, description), resolve a project name to its ID for downstream skills
- Out of scope: Work item lifecycle, pipeline creation/configuration, promotion/deployment, conflict detection (separate skills)
Required Inputs
Gather or infer before proceeding:
- Operation type: list, create, or update
- Target org:
--target-org <alias>is required on every command unless thetarget-orgconfig var is already set (sf config get target-org) - For list: no other required input (lists all projects in the org); optional name filter
- For create: project name (required), description (optional)
- For update: project ID (required), fields to update — at least one of name, description, or active status
Defaults unless specified:
- Output format:
--jsonfor headless consumption - Project identifier: when the user gives a project name for update, resolve it to a project ID first via
sf devops project list --target-org <alias> --json
If the user provides a clear request ("list all projects", "create a project called Release Alpha", "rename project X to Y"), proceed immediately without unnecessary questions.
Workflow
All operations use sf devops project CLI commands with --json output for structured consumption.
Phase 1 — Identify Operation
- Determine the operation type from user intent:
- Keywords like "list", "show", "find", "what projects", "get project ID" → list operation
- Keywords like "create", "new", "set up", "initialize" → create operation
- Keywords like "update", "change", "rename", "modify", "edit" → update operation
Phase 2 — Execute Operation
- Verify org authentication before any operation, checking the same org the operation will target:
# When a specific org is requested, check that alias (do NOT rely on the default org): sf org display --target-org <alias> --json # Only when no alias is supplied and a default org is expected: sf org display --json- If the requested org is not authenticated or authentication has expired, instruct the user to run:
sf org login web --alias <alias> - Verify the authenticated org has DevOps Center enabled by attempting to list projects
--target-org <alias>is required on everysf devops projectcommand unless thetarget-orgconfig var is set (check withsf config get target-org). Add--target-org <alias>to all commands when targeting a specific org — a targeted operation must never require or reset the default org
- If the requested org is not authenticated or authentication has expired, instruct the user to run:
What ships with it
5 files 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.
- 7d ago First seen · 198 lines · 186 tokens per session scan A e12dd7ed256d
dx-devops-project-manage is a skill published in the GitHub repository forcedotcom/sf-skills (987 stars, last pushed yesterday), licensed Apache-2.0. It adds 186 tokens to every session and 3,207 once invoked, about $0.0009 per session on Opus 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-05.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.