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 instructions/thiagoguislotti/copilot-instructions/frontendgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/frontend)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/frontend"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/frontend.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 | $0.02538 | $0.02538 |
| Opus 5 | $0.01269 | $0.01269 |
| Sonnet 5 | $0.00508 | $0.00508 |
| Haiku 4.5 | $0.00254 | $0.00254 |
Grade C, and why
copilot-instructions frontend.instructions.md scanned grade C with 1 finding 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 4d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- ✅ CORRECT: Design system utility when needed --> How it starts
The opening of the file, as written. The whole thing — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture
- Hooks/composables for reactive logic
- Presentational components using props and slots
- Services for pure HTTP requests
- Feature-first Clean Architecture: modules//{domain,application,infrastructure,presentation}
- Shared resources: shared/{domain,application,infrastructure,presentation,utils,constants}
- CSS in SFC: Keep component styles in
<style scoped>within .vue files (Vue 3 best practice) - Prefer Quasar utilities: Use Quasar classes before writing custom CSS
const { rows } = useTablePaging(apiEndpoint);
<UserCard :user="u" v-slot:actions><button>Edit</button></UserCard>
Naming
- Prefix composables with
use* - Never use default exports
- Avoid side effects on import
- Component files in PascalCase:
BaseButton.vue,SearchPage.vue - Composables in camelCase:
useAuth.ts,useFormRules.ts - CSS classes in kebab-case:
search-container,action-buttons
export function useAuth() { /* ... */ } // not export default
// Import modules without executing code automatically
Component Library Pattern
Base Component Naming
- Prefix shared components with
Base*:BaseButton,BaseInput,BaseCard - Use slots for flexible content injection
- Expose consistent prop interfaces across components
- Document props with JSDoc comments
Component Categories
components/
├── form/ # BaseInput, BaseSelect, BaseTextarea, BaseDatePicker, BaseTimePicker
├── layout/ # BaseHeader, BaseFooter, BaseSection, BaseHero, BaseSidebar
└── ui/ # BaseButton, BaseCard, BaseChip, BaseLogo, MetricCard, InfoCard
Export Pattern (Single Entry Point)
// index.ts
export { default as BaseButton } from './components/ui/BaseButton.vue'
export { default as BaseInput } from './components/form/BaseInput.vue'
export * from './composables/ui/useTheme'
export * from './config/theme.config'
Theme System
Multi-Theme Architecture
- Define theme configuration interface with colors, fonts, gradients
- Use CSS custom properties for runtime theme switching
- Implement
useThemecomposable for reactive theme management - Store theme preference in localStorage
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.
- 4d ago First seen · 327 lines · 2,538 tokens per session scan C e9a663f3cd1b
copilot-instructions frontend.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 2,538 tokens to every session, about $0.0127 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.