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.
git clone --depth 1 https://github.com/julianoczkowski/create-trimble-appWrote 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/julianoczkowski/create-trimble-app/pages)<a href="https://agentmods.dev/instructions/julianoczkowski/create-trimble-app/pages"><img src="https://agentmods.dev/badge/instructions/julianoczkowski/create-trimble-app/pages.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.00403 | $0.00403 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
create-trimble-app pages.instructions.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 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.
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
Application Page Patterns
Pages are user-facing application screens in src/pages/.
Page Structure
export default function PageName() {
return (
<div className="min-h-screen bg-background">
{/* Page content */}
<div className="container mx-auto p-6">
<div className="text-2xl font-bold text-foreground mb-6">
Page Title
</div>
{/* Content sections */}
</div>
</div>
);
}
Layout Patterns
Use Tailwind utilities with design system colors:
// Card layout
<div className="bg-card border-default rounded-lg p-6">
{/* Card content */}
</div>
// Grid layout
<div className="grid grid-cols-1 md:grid-cols-2 lg:grid-cols-3 gap-6">
{/* Grid items */}
</div>
Navigation
Add routes in src/App.tsx:
<Route path="/your-page" element={<YourPage />} />
Styling Rules
- Use design system colors only:
bg-background,text-foreground,bg-card - Use opacity utilities:
text-foreground-80(nottext-foreground/80) - Use border utilities:
border-default,border-bottom-default - Use
<div>elements only (noh1,p,section)
Theme Awareness
Pages automatically adapt to the active theme. Use theme context if needed:
import { useTheme } from "@/contexts/ThemeContext";
const { theme, setTheme } = useTheme();
Component Usage
Always use wrapper components from src/components/:
import { ModusButton, ModusAlert, ModusCard } from "@/components";
Never import ModusWc* components directly.
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 · 77 lines · 403 tokens per session scan A d0fae63440a3
create-trimble-app pages.instructions.md is an instructions file published in the GitHub repository julianoczkowski/create-trimble-app (3 stars, last pushed 2mo ago), licensed MIT. It adds 403 tokens to every session, about $0.0020 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 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.