Borrowing it
Nothing to install: this file belongs to abdullah1854/MCPGateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/abdullah1854/MCPGateway/main/.agents/skills/doc-coauthoring/SKILL.mdgit clone --depth 1 https://github.com/abdullah1854/MCPGatewayWrote 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/abdullah1854/mcpgateway/doc-coauthoring)<a href="https://agentmods.dev/skills/abdullah1854/mcpgateway/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/abdullah1854/mcpgateway/doc-coauthoring/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/abdullah1854/mcpgateway/doc-coauthoring"><img src="https://agentmods.dev/badge/skills/abdullah1854/mcpgateway/doc-coauthoring.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.00047 | $0.01238 |
| Opus 5 | $0.00023 | $0.00619 |
| Sonnet 5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
doc-coauthoring 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.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Co-Authoring Skill
When This Skill Activates
- "Write a document", "draft a proposal"
- "Create a spec", "design document"
- "Help me write", "co-author"
- "RFC", "ADR", "technical spec"
- "Documentation", "user guide"
Three-Stage Workflow
Stage 1: Context Gathering
Start with meta-context questions:
- Who is the audience?
- What's the purpose/goal?
- What decisions need to be made?
- What constraints exist?
- What's the deadline/urgency?
Then info dump:
- Ask user to share all relevant context
- Notes, prior docs, requirements
- Stakeholder preferences
- Examples of similar docs they like
Clarifying questions:
- Ask 3-5 targeted questions
- Ensure understanding before drafting
- Surface hidden assumptions
Stage 2: Section-by-Section Drafting
For each section:
1. ASK clarifying questions for this section
2. BRAINSTORM 5-20 options/approaches
3. CURATE down to best options
4. DRAFT the section
5. REFINE based on feedback
Feedback guidance:
- "Specific feedback helps!" not just "looks good"
- "What's missing?" "What's confusing?"
- "What would [stakeholder] push back on?"
Surgical edits:
- Never reprint entire sections
- Use targeted replacements
- Preserve voice and flow
Stage 3: Reader Testing
Fresh perspective test:
- Imagine a reader with NO context
- Can they answer key questions?
- Are there gaps or ambiguities?
- What questions would they ask?
Predicted questions:
Q: What problem does this solve?
A: [Answer from doc - check clarity]
Q: Why this approach vs alternatives?
A: [Answer from doc - check completeness]
Q: What are the risks?
A: [Answer from doc - check thoroughness]
Document Templates
Technical Spec / RFC
# [Feature Name] - Technical Specification
## Status
Draft | Review | Approved | Implemented
## Summary
[1-2 sentence overview]
## Background
[Context and problem statement]
## Goals
- [Goal 1]
- [Goal 2]
## Non-Goals
- [What this does NOT address]
## Proposed Solution
[Detailed description]
### Architecture
[Diagrams, components, data flow]
### API Changes
[Endpoints, schemas, breaking changes]
## Alternatives Considered
### Option A: [Name]
- Pros: [...]
- Cons: [...]
### Option B: [Name]
- Pros: [...]
- Cons: [...]
## Security Considerations
[Auth, data protection, attack vectors]
## Testing Plan
[How to verify correctness]
## Rollout Plan
[Phased rollout, feature flags, rollback]
## Open Questions
- [ ] [Question 1]
- [ ] [Question 2]
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 · 255 lines · 47 tokens per session scan A 9387a60ceb64
doc-coauthoring is a skill published in the GitHub repository abdullah1854/MCPGateway (15 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,238 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
cmdb-patterns
Create ServiceNow CIs and cmdbrelci relationships, walk upstream/downstream impact, detect orphan/stale CIs, and align discovered CIs with the proper sysclassname hierarchy.
blast-radius
Trace ServiceNow configuration dependencies — what artifacts touch a given field, what calls a script include, table/app-level config inventory. Use before deletes, renames, or refactors.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
csm-patterns
Build ServiceNow Customer Service Management — customeraccount, customercontact, sncustomerservicecase routing, service entitlements with usage decrement, and Customer Portal case submission widgets.
discovery-patterns
Configure ServiceNow Discovery — schedules, IP ranges, credential affinities, MID Server assignment, custom probes/sensors, identification rules, and run-status monitoring on discovery tables.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.