CreateFunctionalDocs

CreateFunctionalDocs is a command for coding agents from Evyasys-Software-Solutions/EvyaGovernance. It costs 93 tokens per session (491 once invoked), scanned B, original, MIT.

A project-scanning command that creates plain-language documentation for each business module, including rules, workflows, permissions, errors, and integrations.

In plain words
What is it for?
Use it to document a codebase’s business modules and record how they behave, what access they require, which validations apply, and how they connect to other systems.
Why use it?
It turns scattered implementation details into a consistent reference that people and AI tools can search and understand.

Command

Part of the evyasys plugin — 15 skills, 15 commands shipped together

Install

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.

agentmods
npx agentmods add commands/evyasys-software-solutions/evyagovernance/createfunctionaldocs
Clone the repo
git clone --depth 1 https://github.com/Evyasys-Software-Solutions/EvyaGovernance

Or install evyasys, the plugin that ships this one along with the rest of its 15 skills, 15 commands.

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 CreateFunctionalDocs

README.md
[![agentmods](https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/createfunctionaldocs.svg)](https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/createfunctionaldocs)
Your own site
<a href="https://agentmods.dev/commands/evyasys-software-solutions/evyagovernance/createfunctionaldocs"><img src="https://agentmods.dev/badge/commands/evyasys-software-solutions/evyagovernance/createfunctionaldocs.svg" alt="Measured on agentmods" height="20"></a>
Per session 93 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 491 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original 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 $0.00093 $0.00491
Opus 5 $0.00046 $0.00246
Sonnet 5 $0.00019 $0.00098
Haiku 4.5 $0.00009 $0.00049

Measured 4d ago against content hash ec681f4c41b5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

CreateFunctionalDocs scanned grade B with 1 finding 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 4d 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

EVYA_AI=$(find "$HOME/.claude/plugins" -maxdepth 6 -type d -name ".ai" 2>/dev/null | grep -i "EvyaGovernance" | head -1); [ -z "$EVYA_AI" ] && EVYA_AI=".ai"; echo "$EVYA_AI"
commands/CreateFunctionalDocs.md · 33 lines

What it actually says

You are running /evyasys:CreateFunctionalDocs $ARGUMENTS.

Step 0 — Load workflow

First — find the plugin's installed workflow directory (do this before any file read):

macOS / Linux — run via Bash:

EVYA_AI=$(find "$HOME/.claude/plugins" -maxdepth 6 -type d -name ".ai" 2>/dev/null | grep -i "EvyaGovernance" | head -1); [ -z "$EVYA_AI" ] && EVYA_AI=".ai"; echo "$EVYA_AI"

Windows — run via PowerShell:

$EVYA_AI = (Get-ChildItem "$env:USERPROFILE\.claude\plugins" -Recurse -Directory -Filter ".ai" -ErrorAction SilentlyContinue | Where-Object { $_.FullName -like '*EvyaGovernance*' } | Select-Object -First 1 -ExpandProperty FullName); if (-not $EVYA_AI) { $EVYA_AI = ".ai" }; Write-Output $EVYA_AI

Use the printed path in place of .ai for every workflow file read below. If a file is not found at the plugin path (older install), fall back to the same path under .ai/.

Load these three files from <plugin-ai>/workflows/create-functional-docs/:

  1. AGENT.md — your role and principles
  2. PROMPT.md — the full workflow
  3. MODULE_TEMPLATE.md — the document template

Then follow the workflow in PROMPT.md exactly.

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. 4d ago First seen · 33 lines · 93 tokens per session scan B ec681f4c41b5

Subscribe to this mod's changes

CreateFunctionalDocs is a command published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 22d ago), licensed MIT. It adds 93 tokens to every session and 491 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.