Borrowing it
Nothing to install: this file belongs to kolirt/vue-modal. 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/kolirt/vue-modal/master/AGENTS.mdgit clone --depth 1 https://github.com/kolirt/vue-modalWrote 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/kolirt/vue-modal/agents-md)<a href="https://agentmods.dev/instructions/kolirt/vue-modal/agents-md"><img src="https://agentmods.dev/badge/instructions/kolirt/vue-modal/agents-md.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.04062 | $0.04062 |
| Opus 5 | $0.02031 | $0.02031 |
| Sonnet 5 | $0.00812 | $0.00812 |
| Haiku 4.5 | $0.00406 | $0.00406 |
Grade A, and why
vue-modal AGENTS.md 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 6d 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 — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@kolirt/vue-modal — guide for AI agents
This is a complete, de-styled offline reference for AI coding agents using
@kolirt/vue-modal (Vue 3 headless modal library). Canonical, always-current
docs live at https://kolirt.github.io/vue-modal/. Package version: 2.4.0.
If you only read one section, read this one.
Critical rules (avoid the common mistakes)
- Peer deps: requires
vue >= 3.4andreka-ui >= 2. Install both. - Register the plugin:
app.use(createModal({ groups: { default: {} } })). - Mount a target: put
<ModalTarget group="default" />in your app layout (not behind av-ifthat is false when a modal opens). - Hierarchy: a modal component must render
<ModalRoot>wrapping<ModalContent>. Missing<ModalContent>⇒ the modal is blank and never closes (the exit animation never fires). - Group is required:
openModal(Comp, { group: 'default' }), or declaredefineOptions({ modalGroup: 'default' })on the component. No group ⇒ throws. - Never call
openModalat module scope. Call it from an event handler or insideonMounted. It is client-only; it mutates shared module-level state, so calling it during SSR is unsafe (the state leaks across concurrent requests). - z-index / stacking:
<ModalTarget>has no built-in z-index. Within one group the package stacks modals for you, but to order different groups (aconfirm/promptabove amainmodal) give each group's<ModalTarget>an explicit z-index — a small layered scale (z-40…z-70), not9999. Same if a page's fixed element overlaps the modal. (See the z-index section.) - SSR: the component primitives are SSR-safe and render on the server;
openModalis not — only call it on the client (e.g. insideonMounted).
Minimal correct setup
// main.ts
import { createModal } from '@kolirt/vue-modal'
app.use(createModal({ groups: { default: {} } }))
<!-- App.vue -->
<template>
<RouterView />
<ModalTarget group="default" />
</template>
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.
- 6d ago First seen · 293 lines · 4,062 tokens per session scan A ca704fb64bc7
vue-modal AGENTS.md is an instructions file published in the GitHub repository kolirt/vue-modal (23 stars, last pushed 2mo ago), licensed MIT. It adds 4,062 tokens to every session, about $0.0203 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 instructions, from other repositories
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
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.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.