Borrowing it
Nothing to install: this file belongs to managedcode/GeminiSharpSDK. 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/managedcode/GeminiSharpSDK/main/.codex/skills/mcaf-feature-spec/SKILL.mdgit clone --depth 1 https://github.com/managedcode/GeminiSharpSDKWrote 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/managedcode/geminisharpsdk/mcaf-feature-spec)<a href="https://agentmods.dev/skills/managedcode/geminisharpsdk/mcaf-feature-spec"><img src="https://agentmods.dev/badge/skills/managedcode/geminisharpsdk/mcaf-feature-spec/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/managedcode/geminisharpsdk/mcaf-feature-spec"><img src="https://agentmods.dev/badge/skills/managedcode/geminisharpsdk/mcaf-feature-spec.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.00075 | $0.00612 |
| Opus 5.5 | $0.00030 | $0.00245 |
| Sonnet 5.5 | $0.00015 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
mcaf-feature-spec 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 2mo 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCAF: Feature Spec
Outputs
docs/Features/<feature>.md(create or update)- Update links from/to ADRs and architecture map when needed
Spec Quality (anti-guesswork checklist)
Write a spec that can be implemented and verified without guessing:
- No placeholders: avoid “TBD”, “later”, “etc.”; if something is unknown, list it as an explicit question.
- Concrete modules: use real module/boundary names from
docs/Architecture/Overview.md. - Rules are testable: numbered business rules with clear inputs → outputs (no vague adjectives).
- Flows are executable: scenarios include preconditions, steps, expected results (happy + negative + edge).
- Verification is real: commands copied from
AGENTS.md, and scenarios mapped to test IDs. - Stakeholders covered: Product / Dev / DevOps / QA each get the information they need to ship safely.
Workflow
- Start from
docs/Architecture/Overview.mdto pick the affected module(s). - Create/update the feature doc using
docs/templates/Feature-Template.md.- follow
AGENTS.mdscoping rules (do not scan the whole repo; use the architecture map to stay focused) - keep the feature’s
## Implementation plan (step-by-step)updated while executing
- follow
- Define behaviour precisely:
- purpose and scope (in/out)
- business rules (numbered, testable)
- primary flow + edge cases
- Describe system behaviour in terms of entry points, reads/writes, side effects, idempotency, and errors.
- Add a Mermaid diagram for the main flow (modules + interactions; keep it readable).
- Write verification that can be executed:
- test environment assumptions
- concrete test flows (positive/negative/edge)
- mapping to where tests live (or will live)
- traceability: rules/flows → test IDs (so tests reflect the spec)
- Keep Definition of Done strict:
- behaviour covered by automated tests
- static analysis clean
- docs updated (feature + ADR + architecture overview if boundaries changed)
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.
- 2mo ago First seen · 51 lines · 75 tokens per session scan A 7aeb0a2d0713
mcaf-feature-spec is a skill published in the GitHub repository managedcode/GeminiSharpSDK (2 stars, last pushed 2d ago), licensed MIT. It adds 75 tokens to every session and 612 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
csharp-expert
Expert-level C# development with .NET 8+, ASP.NET Core, LINQ, async/await, and enterprise patterns. Use when the user mentions C#, .NET, ASP.NET, enterprise, or Microsoft platforms, or when the task involves Modern C#, Async/Await, LINQ, or ASP.NET Core.
security-patcher
Invoke this as your absolute first action before using any other tools whenever a user requests to fix, patch, or remediate a vulnerability. Do not perform manual research first.
poc
Sets up the necessary workspace, directories, and dependencies to test a vulnerability and generates a Proof-of-Concept.
dependency-manager
Safely resolve and install isolated dependencies for isolated sandboxes (PoC execution).
azure-mgmt-apicenter-dotnet
Azure API Center SDK for .NET. Centralized API inventory management with governance, versioning, and discovery. Use for creating API services, workspaces, APIs, versions, definitions, environments, deployments, and metadata schemas. Triggers: "API Center", "ApiCenterService", "ApiCenterWorkspace", "ApiCenterApi", "API…
azure-resource-manager-postgresql-dotnet
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for…