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 skills add scott-fryxell/brayness --skill vue-inspectgit clone --depth 1 https://github.com/scott-fryxell/braynessWrote 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/scott-fryxell/brayness/vue-inspect)<a href="https://agentmods.dev/skills/scott-fryxell/brayness/vue-inspect"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/vue-inspect/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/skills/scott-fryxell/brayness/vue-inspect"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/vue-inspect.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.00068 | $0.00758 |
| Opus 5 | $0.00034 | $0.00379 |
| Sonnet 5 | $0.00014 | $0.00152 |
| Haiku 4.5 | $0.00007 | $0.00076 |
Grade A, and why
vue-inspect 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vue-inspect
Vue 3 exposes its whole runtime state on plain DOM nodes and component instances - no
extension required. This skill is a set of copy-pasteable eval snippets (run via
agent-browser eval "(() => { ... })()") that walk that internal state to answer
"what does this component actually think its data is right now."
It exists because agent-browser has native React Devtools integration
(--enable react-devtools + react tree/react inspect/react renders) but nothing
built in for Vue. These snippets close that gap using Vue 3's own internals directly.
When to use
- Runtime-dependent state: what a ref/prop/computed actually is right now (mid-animation, post-interaction), what's actually mounted, whether a component exists in the rendered tree at all.
- Not for static reads - prop definitions and template markup live in the source file; go read it instead.
Quick start
Confirm the page is a Vue 3 app and get the version:
agent-browser eval "document.querySelector('#app').__vue_app__.version"
If #app isn't the mount point, find it: Vue attaches __vue_app__ to whatever
element was passed to app.mount(...). document.querySelector('[data-v-app]') or
inspecting the root of the visible DOM tree usually finds it if the id differs.
Full reference snippets (tree walker, name-finder, state reader) live in
references/api-surface.md - copy them directly into an
eval call.
The one gotcha that will cost you time
setupState auto-unwraps top-level refs. setup.some_ref is the raw value
(0, false, {...}), not a ref object - setup.some_ref?.value silently returns
undefined. Check typeof setup.some_ref before assuming you need .value. Full
explanation in references/troubleshooting-workarounds.md.
Files
- references/api-surface.md - the internal properties
(
__vue_app__,subTree,setupState,type.name) and the three core snippets (tree walker, name-finder, state reader). - references/common-use-cases.md - worked examples:
reading a ref, finding a
v-forinstance, checking props, confirming mount/unmount, reading provide/inject, catching a mid-animation state. - references/troubleshooting-workarounds.md - known failure modes (ref unwrapping, functional components, Teleport/Suspense/KeepAlive, multiple apps, Vue 2 differences, prod build name-mangling) with fixes.
What ships with it
4 files 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.
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.
- 12d ago First seen · 64 lines · 68 tokens per session scan A 7f46905b8b4b
vue-inspect is a skill published in the GitHub repository scott-fryxell/brayness (121 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 758 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-30.
Other skills, from other repositories
shadcn-svelte
Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
v3-create-crud
A page generator for standard create, read, update, and delete screens, commonly called CRUD screens. It uses Element Plus, a Vue user-interface library, to build tables, searches, pagination, forms, and delete confirmations.
v3-use-composables
Documentation for reusable Vue functions in a project, covering device detection, asynchronous dropdown data, loading screens, pagination, routing, themes, page titles, and watermarks.
moai-domain-uiux
UI/UX design systems specialist covering accessibility, icons, theming, design tokens, and user experience patterns. Use when working on design systems, WCAG compliance, ARIA patterns, or dark mode theming.
frontend-conventions
Frontend convention reference (SvelteKit / Svelte 5). Auto-injected into frontend-aware agents - not user-invocable.