Borrowing it
Nothing to install: this file belongs to Evyasys-Software-Solutions/EvyaGovernance. 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/Evyasys-Software-Solutions/EvyaGovernance/main/CLAUDE.mdgit clone --depth 1 https://github.com/Evyasys-Software-Solutions/EvyaGovernanceWrote 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/instructions/evyasys-software-solutions/evyagovernance/claude-md)<a href="https://agentmods.dev/instructions/evyasys-software-solutions/evyagovernance/claude-md"><img src="https://agentmods.dev/badge/instructions/evyasys-software-solutions/evyagovernance/claude-md/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/instructions/evyasys-software-solutions/evyagovernance/claude-md"><img src="https://agentmods.dev/badge/instructions/evyasys-software-solutions/evyagovernance/claude-md.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.07170 | $0.07170 |
| Opus 5.5 | $0.02868 | $0.02868 |
| Sonnet 5.5 | $0.01434 | $0.01434 |
| Haiku 4.5 | $0.00717 | $0.00717 |
Grade A, and why
EvyaGovernance CLAUDE.md scanned grade A 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 13d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
import urllib.parse How it starts
The opening of the file, as written. The whole thing — 576 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EvyaGovernance — Claude Code Project Standards
This file is the authoritative reference for all code generation, review, and modification in this repository. Read it completely before writing a single line.
1. Project Overview
EvyaGovernance is an AI-assisted SDLC delivery pipeline built by Evyasys Software Solutions. It integrates Claude Code skills with Azure DevOps and Microsoft Teams to automate the full story lifecycle: Plan (epic → stories → tasks) → Build (dev, review, checks) → Qa (test, sign-off).
Architecture layers (top to bottom)
Claude Agent (AI prompt + agent result)
↓
skills/evyasys-*/hooks.js orchestration — save artefacts, confirm, call integrations
↓
scripts/lib/ utilities — config, ado-map, dryrun, markdown-to-html
↓
scripts/integrations/ external service clients — azure_devops, teams_webhook
↓
.evyasys/ per-project runtime state — board/, .ado-map.json, project.yaml
↓
Azure DevOps API / Teams webhook external systems
Never cross layers upward. A lib utility must not import a hook. An integration must not import another integration. State flows downward only.
2. Folder Structure
/
├── .ai/ AI control plane (Git-backed, shared with team)
│ ├── core/ Quality gates, output contract, human confirmation rules
│ ├── rules/ Coding and naming standards applied by every workflow
│ ├── workflows/ Per-command: PROMPT.md, AGENT.md, CHECKLIST.md, templates
│ └── manifest.yaml Plugin defaults (work-item types, dry-run flag)
├── .evyasys/ Per-project runtime (generated, committed)
│ ├── board/ Artefacts: epics/{id}/stories/{id}/ or stories/{id}/
│ ├── .ado-map.json Evyasys ID → ADO numeric ID + directory mapping
│ └── project.yaml Project config: org, ADO project, Teams webhook
├── commands/ User-facing command definitions (PascalCase.md)
├── scripts/
│ ├── lib/ Reusable utilities (kebab-case.js / snake_case.py)
│ └── integrations/ External API clients (azure_devops.js/.py, teams_webhook.js)
└── skills/
└── evyasys-<command>/ One folder per skill: hooks.js + SKILL.md
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.
- 13d ago Changed · +10 lines · +618 tokens per session 77d9ef7cb80b
- 17d ago Changed · +37 lines · +1,273 tokens per session 8f06fd23d0df
- 19d ago Changed · +48 lines · +853 tokens per session 5db1d935c352
- 1mo ago First seen · 481 lines · 4,426 tokens per session scan A de945c09cb82
EvyaGovernance CLAUDE.md is an instructions file published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 14d ago), licensed MIT. It adds 7,170 tokens to every session, about $0.0287 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.