orkia: Skill for Claude Code

.agents/skills/write-orkia-rfc/SKILL.md

write-orkia-rfc is a skill for Claude Code, Codex from orkiaHQ/orkia. It costs 42 tokens per session (1,784 once invoked), scanned A, original, no licence file.

An RFC-writing tool for turning a GitHub issue into a public Orkia proposal. An RFC is a document that explains a proposed change so others can review it.

In plain words
What is it for?
Opening an RFC for an Orkia repository issue and completing its written content.
Why use it?
It gives contributors a starting structure and helps turn an issue into a reviewable proposal.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing. Also seen: installed under .agents/ (shared by several agents).

This is orkiaHQ/orkia's own configuration. It tells Claude Code and Codex how to work on orkia itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything orkia configures →

Reuse

Borrowing it

Nothing to install: this file belongs to orkiaHQ/orkia. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/orkiaHQ/orkia/main/.agents/skills/write-orkia-rfc/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/orkiaHQ/orkia

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for write-orkia-rfc

README.md
[![agentmods](https://agentmods.dev/badge/skills/orkiahq/orkia/write-orkia-rfc/github.svg)](https://agentmods.dev/skills/orkiahq/orkia/write-orkia-rfc)
Your own site
<a href="https://agentmods.dev/skills/orkiahq/orkia/write-orkia-rfc"><img src="https://agentmods.dev/badge/skills/orkiahq/orkia/write-orkia-rfc/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.

agentmods 80×15 button for write-orkia-rfc

Your own site · 80×15
<a href="https://agentmods.dev/skills/orkiahq/orkia/write-orkia-rfc"><img src="https://agentmods.dev/badge/skills/orkiahq/orkia/write-orkia-rfc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,784 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.01784
Opus 5 $0.00021 $0.00892
Sonnet 5 $0.00008 $0.00357
Haiku 4.5 $0.00004 $0.00178

Measured 9d ago against content hash 19ea94f8281d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

write-orkia-rfc 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.

.agents/skills/write-orkia-rfc/SKILL.md · 145 lines

The source is not reproduced here

A licence we could not identify

The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.

Read it on GitHub

Changes

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.

  1. 9d ago First seen · 145 lines · 42 tokens per session scan A 19ea94f8281d

Subscribe to this mod's changes

write-orkia-rfc is a skill published in the GitHub repository orkiaHQ/orkia (5 stars, last pushed 2mo ago), with no licence file. It adds 42 tokens to every session and 1,784 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-31.

Related

Other skills, from other repositories

resolve-conflicts

Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling…

tailcallhq/forgecode · 68 tokens

github-pr-description

Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it…

tailcallhq/forgecode · 72 tokens

debug-cli

Use when users need to debug, modify, or extend the code-forge application's CLI commands, argument parsing, or CLI behavior. This includes adding new commands, fixing CLI bugs, updating command options, or troubleshooting CLI-related issues.

tailcallhq/forgecode · 49 tokens

resolve-fixme

Find all FIXME comments across the codebase and fully implement the work they describe. Use when the user asks to fix, resolve, or address FIXME comments, or when running the "fixme" command. Runs a discovery script to find every FIXME, expands multiline comment blocks, groups related FIXMEs across files into a single…

tailcallhq/forgecode · 100 tokens

write-release-notes

Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes…

tailcallhq/forgecode · 105 tokens

create-github-issue

Create GitHub issues using GitHub CLI with support for templates, labels, assignees, milestones, and draft issues. Use when the user asks to create a GitHub issue, file a bug report, submit a feature request, or open an issue in a GitHub repository.

tailcallhq/forgecode · 63 tokens