Borrowing it
Nothing to install: this file belongs to vaquarkhan/Fullstack-development-agent-skills. 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/vaquarkhan/Fullstack-development-agent-skills/main/.kiro/steering/README.mdgit clone --depth 1 https://github.com/vaquarkhan/Fullstack-development-agent-skillsWrote 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/vaquarkhan/fullstack-development-agent-skills/readme)<a href="https://agentmods.dev/instructions/vaquarkhan/fullstack-development-agent-skills/readme"><img src="https://agentmods.dev/badge/instructions/vaquarkhan/fullstack-development-agent-skills/readme.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.00066 | $0.00066 |
| Opus 5 | $0.00033 | $0.00033 |
| Sonnet 5 | $0.00013 | $0.00013 |
| Haiku 4.5 | $0.00007 | $0.00007 |
Grade A, and why
Fullstack-development-agent-skills README.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 today.
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
Kiro Steering Adapter
This directory adapts the fullstack lifecycle for Kiro steering workflows.
Primary entry:
skills/using-fullstack-agent-skills/SKILL.md
Recommended command flow:
/spec->/plan->/build->/validate->/review->/ship
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.
- today First seen · 12 lines · 66 tokens per session scan A f4a144d0107f
Fullstack-development-agent-skills README.md is an instructions file published in the GitHub repository vaquarkhan/Fullstack-development-agent-skills (2 stars, last pushed yesterday), licensed MIT. It adds 66 tokens to every session, 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-09-07.
Other instructions, from other repositories
graftcode graftcode-dotnet.instructions.md
Instructions for grft-dev/graftcode, covering graftcode — .net backend services, when this applies (always), authoritative docs (source of truth), golden rules and service = .net class library.
graftcode graftcode-python.instructions.md
Instructions for grft-dev/graftcode, covering graftcode — python backend services, when this applies (always), authoritative docs (source of truth), golden rules and service = plain python module (no web framework).
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).
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.