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.
npx agentmods add skills/s977043/river-review/code-vuenpx skills add s977043/river-review --skill code-vuegit clone --depth 1 https://github.com/s977043/river-reviewWrote 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/skills/s977043/river-review/code-vue)<a href="https://agentmods.dev/skills/s977043/river-review/code-vue"><img src="https://agentmods.dev/badge/skills/s977043/river-review/code-vue.svg" alt="Measured on agentmods" 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.00022 | $0.00853 |
| Opus 5 | $0.00011 | $0.00426 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
Component Test Scaffold (Vue.js) 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 2d 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.
What it actually says
Pattern declaration
Primary pattern: Generator Secondary patterns: Inversion Why: 仕様書からVue.jsコンポーネントテストの足場を生成するジェネレーターであり、仕様の抜けをテスト観点から逆照射する。
Role
あなたは熟練したVue.js開発者です。 仕様書で定義されたUI/UX要件を満たすための「コンポーネントテストのスケルトンコード(Vue Test Utils)」を作成してください。
Non-goals / 扱わないこと
- 実装ロジックや最適化方針は指示しない。
- E2E/統合テストの網羅は対象外で、コンポーネント単位の足場に限定する。
Pre-execution Gate / 実行前ゲート
このスキルは以下の条件がすべて満たされない限りNO_REVIEWを返す。
- 差分に仕様書(
docs/**/*.mdまたはspecs/**/*.md)が含まれている - 仕様書にVue.jsコンポーネントに関する記述がある
- inputContextにfullFileが含まれている
ゲート不成立時の出力: NO_REVIEW: code-vue — 対象となるVue.jsコンポーネント仕様が差分に含まれていない
False-positive guards / 抑制条件
- 仕様に記載のない要件を推測で追加しない。
- 対象外と明記された領域(例: 外部API連携の実装詳細)への指摘は行わない。
Output Format
TypeScript/JavaScript のコードブロック。
mount または shallowMount を使用したテストケースを作成します。
describe ブロックで構成し、各テストケース (it) 内に // TODO で検証ステップを記述してください。
Example
import { mount } from '@vue/test-utils';
import { describe, it, expect } from 'vitest';
import UserProfile from '@/components/UserProfile.vue';
describe('UserProfile.vue', () => {
it('renders user name when passed via props', () => {
// TODO: Arrange (mount component with props)
// const wrapper = mount(UserProfile, { props: { name: 'Alice' } })
// TODO: Assert text content
// expect(wrapper.text()).toContain('Alice')
});
it('emits "update" event on button click', async () => {
// TODO: Arrange & Act (find button and trigger click)
// await wrapper.find('button').trigger('click')
// TODO: Assert event emission
// expect(wrapper.emitted()).toHaveProperty('update')
});
});
Constraints
- テストランナーは Vitest を想定してください(Jestの場合はその旨をコメントで補足)。
- コンポーネントの
props、slots、emitイベントの検証を重点的に洗い出してください。 - 非同期更新(
nextTickやawait trigger)が必要な操作については適切なasync/await構文を使用してください。
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.
- 2d ago First seen · 84 lines · 22 tokens per session scan A 18604dd81b6a
Component Test Scaffold (Vue.js) is a skill published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 853 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
laravel-testing
Use when testing controllers, services, or models, or implementing TDD on Laravel 13 with Pest 4 / PHPUnit 12.
ui-development
Build UI pages and extensions for Falcon Foundry apps using React or Vue with the Shoelace design system and Foundry-JS. TRIGGER when user asks to "create a UI page", "build a UI extension", "add a Shoelace component", "call an API from the UI", runs foundry ui pages create or foundry ui run, or needs help with Vite…
vue-component-testing
Applies the three-tier test taxonomy for Vue 3 applications: writes unit tests for composables and Pinia stores with Vitest, component tests for behaviour and user interactions with @testing-library/vue, and acceptance tests for full user flows with Playwright. Ensures tests focus on observable behaviour, not…
improving-tests
Improve test design, speed, and coverage with behavior-focused tests, useful seams, characterization tests, TDD, and test refactoring. Use when improving tests, optimizing slow suites, adding coverage, refactoring brittle tests, removing test waste, or working test-first. NOT for fixing production bugs (use…
mk:vue-testing-best-practices
Use for Vue 3 testing best-practices review and recommendations — designing and auditing Vitest + Vue Test Utils tests for components, composables, Pinia stores, Vue Router, async/Suspense, Teleport, forms, and accessibility, plus Playwright E2E test-design strategy. Advisory/review only — recommends patterns and…
dhpk-tdd-workflow
Framework-agnostic test-driven development guidance for behavior-first unit and integration tests, test scaffolds, and minimal RED-GREEN-REFACTOR changes. Use when building a feature or fixing a bug test-first, writing a test scaffold, or reviewing test seams and mocks. Not for: Playwright journey authoring, pure…