ava: Skill for Claude Code

.claude/skills/ava-mcp-usage/SKILL.md

ava-mcp-usage is a skill for Claude Code from yutakobayashidev/ava. It costs 63 tokens per session (867 once invoked), scanned A, original, MIT.

A guide for using Ava, a task-tracking service connected through MCP tools, to report coding progress.

In plain words
What is it for?
Use it to start tasks, record milestones such as code or test changes, report problems, and finish tracked work.
Why use it?
It helps keep task updates consistent and tells you when to report progress, blockers, and completion.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

This is yutakobayashidev/ava's own configuration. It tells Claude Code how to work on ava 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 ava configures →

Reuse

Borrowing it

Nothing to install: this file belongs to yutakobayashidev/ava. 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/yutakobayashidev/ava/main/.claude/skills/ava-mcp-usage/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/yutakobayashidev/ava

Made for: Claude Code.

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 ava-mcp-usage

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/yutakobayashidev/ava/ava-mcp-usage"><img src="https://agentmods.dev/badge/skills/yutakobayashidev/ava/ava-mcp-usage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 867 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.00063 $0.00867
Opus 5 $0.00032 $0.00434
Sonnet 5 $0.00013 $0.00173
Haiku 4.5 $0.00006 $0.00087

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

Security

Grade A, and why

ava-mcp-usage 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.

.claude/skills/ava-mcp-usage/SKILL.md · 131 lines

How it starts

The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Ava MCP Usage

Overview

Ava provides MCP tools for automatic progress reporting to Slack. This skill shows you how to use these tools effectively with minimal mental burden while maintaining privacy.

Core Philosophy

Ava works best when you tell it what to watch: "Keep an eye on this work."

Important: Treat any coding work as a task, even if the user doesn't explicitly say "task". When the user starts working on something, that's a task to track.

Key principles:

  • Treat all coding work as tasks worth tracking
  • Report only the current task
  • Proactive, frequent updates: Report progress at every meaningful milestone without waiting for user prompts
  • Update granularly: schema changes, file edits, endpoint implementations, test additions - all worth reporting
  • Ask for help immediately when blocked
  • Ask user for consent before marking tasks complete
  • Short commands are sufficient
  • One task per session: If starting different work while a task is active, ask the user if they want to complete the current task first or start a new Claude Code session for the new work

MCP Tools Quick Reference

start_task

Tell Ava what you're working on now. Treat any coding work as a task, even if not explicitly called a "task".

Start task: ログインのエラー処理改善

Tips:

  • Treat all coding work as tasks worth tracking
  • Only report the task you're currently working on
  • Be specific but concise
  • Ava will create a Slack thread for this task
  • Before starting a new task: If there's already an active task in this session, ask the user: "Should I complete the current task first, or would you like to start a new Claude Code session for this different work?"

update_task

Report progress proactively at every meaningful milestone, even without user prompts.

Update task: リトライ実装が完了

When to update (proactively):

  • After creating or editing a schema file
  • After implementing an endpoint or API route
  • After adding validation logic
  • After writing tests
  • After fixing a bug or error
  • After refactoring a component
  • Any other meaningful progress point

Read the full file on GitHub · 131 lines

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 · 131 lines · 63 tokens per session scan A cd69bd757cbb

Subscribe to this mod's changes

ava-mcp-usage is a skill published in the GitHub repository yutakobayashidev/ava (9 stars, last pushed 4mo ago), licensed MIT. It adds 63 tokens to every session and 867 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.

Related

Other skills, from other repositories

daily-briefing

Start your day with a prioritized CRM briefing — works for any monday CRM setup: pipeline, contacts, accounts, leads, or no board at all. Use when someone says 'morning briefing', 'daily brief', 'what's on my plate today', 'catch me up on my deals', 'what needs attention', 'what needs my attention', 'anything urgent…

mondaycom/mcp · 106 tokens

meeting-to-deal

Turn meeting transcripts into deal updates — key points, commitments, and next steps posted to matching CRM deals automatically. Auto-creates contacts for new attendees. Use when someone says "log my meetings to deals", "update CRM from calls", "what did I commit to in meetings", "sync notetaker", "log this meeting"…

mondaycom/mcp · 107 tokens

Technical Debt Tracking with PMAT

Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…

paiml/paiml-mcp-agent-toolkit · 123 tokens

add-a-lib

Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…

lonormaly/builders-stack · 81 tokens

pipefy-members-email-webhooks

Use this skill when the user wants to manage pipe membership, send or read card inbox emails, use email templates, or manage webhooks. Covers 12 MCP tools.

pipefy/ai-toolkit · 41 tokens

pipefy-relations

Use this skill when the user wants to link pipes, tables, or cards across workflows — creating or managing pipe relations, table relations, or card relations. Covers 8 MCP tools.

pipefy/ai-toolkit · 42 tokens