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 nota-america/forgecat-agent-profiles --skill process-docgit clone --depth 1 https://github.com/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/process-doc)<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/process-doc"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/process-doc/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/nota-america/forgecat-agent-profiles/process-doc"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/process-doc.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.00064 | $0.00621 |
| Opus 5 | $0.00032 | $0.00311 |
| Sonnet 5 | $0.00013 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
process-doc 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 9d 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
88% identical to process-doc — 9 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/process-doc
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (
.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_operations/CONNECTORS.md).
Document a business process as a complete standard operating procedure (SOP).
Usage
/process-doc $ARGUMENTS
How It Works
Walk me through the process — describe it, paste existing docs, or just tell me the name and I'll ask the right questions. I'll produce a complete SOP.
Output
## Process Document: [Process Name]
**Owner:** [Person/Team] | **Last Updated:** [Date] | **Review Cadence:** [Quarterly/Annually]
### Purpose
[Why this process exists and what it accomplishes]
### Scope
[What's included and excluded]
### RACI Matrix
| Step | Responsible | Accountable | Consulted | Informed |
|------|------------|-------------|-----------|----------|
| [Step] | [Who does it] | [Who owns it] | [Who to ask] | [Who to tell] |
### Process Flow
[ASCII flowchart or step-by-step description]
### Detailed Steps
#### Step 1: [Name]
- **Who**: [Role]
- **When**: [Trigger or timing]
- **How**: [Detailed instructions]
- **Output**: [What this step produces]
#### Step 2: [Name]
[Same format]
### Exceptions and Edge Cases
| Scenario | What to Do |
|----------|-----------|
| [Exception] | [How to handle it] |
### Metrics
| Metric | Target | How to Measure |
|--------|--------|----------------|
| [Metric] | [Target] | [Method] |
### Related Documents
- [Link to related process or policy]
If Connectors Available
If ~~knowledge base is connected:
- Search for existing process documentation to update rather than duplicate
- Publish the completed SOP to your wiki
If ~~project tracker is connected:
- Link the process to related projects and workflows
- Create tasks for process improvement action items
Tips
- Start messy — You don't need a perfect description. Tell me how it works today and I'll structure it.
- Include the exceptions — "Usually we do X, but sometimes Y" is the most valuable part to document.
- Name the people — Even if roles change, knowing who does what today helps get the process right.
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.
- 9d ago First seen · 86 lines · 64 tokens per session scan A cbd98a0c7bdd
process-doc is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 621 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to process-doc, differing in 9 lines, and is treated as a copy.
Other skills, from other repositories
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.
remove
Remove a deployed framework or addon from the current workspace.
maggy
Maggy is a local AI engineering command center. AI-prioritized inbox across issue trackers (GitHub Issues/Asana), one-click TDD execute with iCPG context enrichment, daily competitor intelligence briefing.
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
executar-minha-revisao-operacional
Reúna o que foi entregue e o que avançou em toda a sua superfície operacional. Escolha o que você precisa: uma revisão semanal que agrega a saída de cada habilidade, cruza prioridades e renovações, sinaliza lacunas e recomenda o próximo movimento; ou um resumo de métricas que percorre cada métrica monitorada, calcula…