Borrowing it
Nothing to install: this file belongs to Huzaifa-ali/post-kit. 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/Huzaifa-ali/post-kit/master/.kiro/steering/frontend.mdgit clone --depth 1 https://github.com/Huzaifa-ali/post-kitWrote 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/huzaifa-ali/post-kit/frontend)<a href="https://agentmods.dev/instructions/huzaifa-ali/post-kit/frontend"><img src="https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/frontend/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/instructions/huzaifa-ali/post-kit/frontend"><img src="https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/frontend.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.01693 | $0.01693 |
| Opus 5.5 | $0.00677 | $0.00677 |
| Sonnet 5.5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
post-kit frontend.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 16d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend — HTML, Tailwind CSS v4, Vanilla JS
Write frontend code like Stripe's dashboard, Linear's UI, or Cal.com: minimal, fast, readable. No cleverness.
Single Responsibility
- One JS file = one concern (
chat.jshandles chat,editor.jshandles editing — never both) - One HTML template = one page
- One component partial = one reusable piece
- One function = one action (fetch data OR render DOM — not both in the same function)
The test: Can you name the file/function in 2-3 words that fully describe it? If not, it does too much.
HTML — Semantic, Accessible, Clean
<!-- Good — semantic, readable -->
<main class="flex-1 p-6">
<section data-page="library">
<header class="mb-6">
<h1 class="text-xl font-semibold text-primary">Library</h1>
</header>
<article class="post-card" data-post-id="{{ post.id }}">
...
</article>
</section>
</main>
<!-- Bad — div soup -->
<div class="main">
<div class="section">
<div class="header">
<div class="title">Library</div>
</div>
</div>
</div>
Rules:
- Semantic elements:
<nav>,<main>,<section>,<article>,<aside>,<header>,<footer> - Every
<img>hasalt. Every<input>has<label>. Every button is keyboard-accessible. data-*attributes for JS hooks. Never select by styling classes.- No inline styles. No inline scripts.
Tailwind CSS v4 — CSS-First, Token-Based
Configuration lives in CSS (not JavaScript)
/* app.css — the ONLY place design tokens are defined */
@import "tailwindcss";
@theme {
/* Colors — OKLCH for perceptual uniformity */
--color-surface: oklch(0.13 0.01 260);
--color-surface-raised: oklch(0.18 0.01 260);
--color-text-primary: oklch(0.93 0 0);
--color-text-secondary: oklch(0.65 0 0);
--color-accent: oklch(0.65 0.19 265);
--color-border: oklch(0.28 0.01 260);
--color-status-draft: oklch(0.75 0.15 85);
--color-status-approved: oklch(0.65 0.15 250);
--color-status-published: oklch(0.70 0.15 145);
/* Typography */
--font-sans: "Inter", system-ui, sans-serif;
--font-mono: "JetBrains Mono", monospace;
/* Shadows */
--shadow-card: 0 2px 8px oklch(0 0 0 / 0.25);
}
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.
- 16d ago First seen · 194 lines · 1,693 tokens per session scan A 1a9d508950fd
post-kit frontend.md is an instructions file published in the GitHub repository Huzaifa-ali/post-kit (4 stars, last pushed 17d ago), licensed MIT. It adds 1,693 tokens to every session, about $0.0068 per session on Opus 5.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-10-11.
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.