agentmods.dev

evyasys-setup

evyasys-setup is a skill for Claude Code from Evyasys-Software-Solutions/EvyaGovernance. It costs 56 tokens per session (522 once invoked), scanned A, original, MIT.

A setup wizard for configuring a project’s project-management and notification tools, such as JIRA, GitHub Projects, Slack, or email.

In plain words
What is it for?
Use it to choose integrations, enter project and notification credentials, verify that they work, and save project settings.
Why use it?
It checks existing settings, asks only for missing information, validates credentials with live requests, and saves the configuration for later workflows.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

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

not rated 7repo 28d ago A scan 56 tokens original MIT

Good fit Use it to choose integrations, enter project and notification credentials, verify that they work, and save project settings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/evyasys-software-solutions/evyagovernance/evyasys-setup
View source ↗ Evyasys-Software-Solutions/EvyaGovernance evyasys.com
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.

Any agent
npx skills add Evyasys-Software-Solutions/EvyaGovernance --skill evyasys-setup
Clone the repo
git clone --depth 1 https://github.com/Evyasys-Software-Solutions/EvyaGovernance

Made for: Claude Code.

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 evyasys-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-setup/github.svg)](https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-setup)
Your own site
<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-setup"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-setup/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 evyasys-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/evyasys-software-solutions/evyagovernance/evyasys-setup"><img src="https://agentmods.dev/badge/skills/evyasys-software-solutions/evyagovernance/evyasys-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 522 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 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.1 $0.00056 $0.00522
Opus 5 $0.00028 $0.00261
Sonnet 5 $0.00011 $0.00104
Haiku 4.5 $0.00006 $0.00052

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

Security

Grade A, and why

evyasys-setup 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 10d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (hooks.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/evyasys-setup/SKILL.md · 49 lines

What it actually says

evyasys:Setup

One-time (or update) configuration wizard for a project.

Agent workflow

Read and follow these two files in order:

  1. .ai/workflows/setup/AGENT.md — agent role, rules, and constraints
  2. .ai/workflows/setup/PROMPT.md — exact question sequence, credential validation commands, and the EVYACONFIG block format to output at the end

Do not skip loading these files. The EVYACONFIG output block is what the post-agent hook uses to save credentials and project config — without it, nothing is persisted.

What it does

  1. Checks .evyasys/project.yaml for existing config — only asks for values that are missing. Shows existing config first.
  2. Prompts you to choose a Project Management Tool: Local folder only / Azure DevOps / JIRA / GitHub Projects.
  3. Collects the credentials and project identifiers for the chosen PM tool.
  4. Validates the PM credentials immediately with a live API call — shows ✅/❌ and asks to re-enter if invalid.
  5. Prompts you to choose a Notification Tool: None / Teams / Slack / WhatsApp / Email.
  6. Collects the webhook URL or messaging credentials for the chosen notification tool.
  7. Validates the notification credentials immediately (sends a test message to Teams/Slack channels, or verifies Twilio/SMTP connection).
  8. Shows a confirmation summary before saving anything.
  9. Outputs a <!-- EVYACONFIG { ... } --> block — the hook parses this and saves config to .evyasys/project.yaml and credentials (encrypted) to ~/.evyasys/credentials.

When to run it

  • First time setting up Evyasys in a new project folder.
  • When switching PM tools or notification channels.
  • When credentials expire or change.

Output

Configuration is persisted by the post-agent hook. The agent does not write files — it outputs the structured EVYACONFIG block and the hook saves everything.

Usage

/evyasys:Setup

No arguments needed.

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 10d ago First seen · 49 lines · 56 tokens per session scan A f29d8ab6bcf8

Subscribe to this mod's changes

evyasys-setup is a skill published in the GitHub repository Evyasys-Software-Solutions/EvyaGovernance (7 stars, last pushed 28d ago), licensed MIT. It adds 56 tokens to every session and 522 once invoked, about $0.0003 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.

Claude CodeProject managementadlcaiai-coding-assistantcompression
Related

Other skills, from other repositories

product-manager-toolkit

Use when the user needs product management workflows such as RICE prioritization, customer interview analysis, PRD templates, discovery frameworks, go-to-market strategy, feature prioritization, research synthesis, or requirements documentation.

majiayu000/spellbook · 47 tokens

weekly

A weekly-report workflow that combines Git history with records from Claude Code and Codex sessions. It turns work from a selected date range into a report for two related software repositories.

majiayu000/spellbook · 41 tokens

task-graph

Execute an approved multi-task plan as a verified DAG with @taskgraph — parallel squad workers per task, validation gates the engine runs itself, and an independent reviewer verdict before any task counts as done. Use for deliveries of 5+ tasks with real independence between them; for smaller work dispatch workers…

diillson/chatcli · 69 tokens

linear

Manage Linear issues from the terminal via the official GraphQL API and the user's API key — list/search issues, create issues, update status/assignee, add comments. Use when asked to "create a Linear issue", "what's assigned to me in Linear", "move this issue to done", "comment on LIN-123".

diillson/chatcli · 69 tokens

lov-rename-project

A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.

lovstudio/skills · 45 tokens

lov-repo2docs

Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…

lovstudio/skills · 186 tokens