post-kit: Instructions file for Kiro

.kiro/steering/git-workflow.md

post-kit git-workflow.md is an instructions file for Kiro from Huzaifa-ali/post-kit. It costs 304 tokens per session, scanned A, original, MIT.

A set of Git contribution rules for branches, commit messages, code quality, and pull requests. Git records code history, while a pull request is a proposed change for review.

In plain words
What is it for?
Use it to choose branch names, write commit messages, check files before committing, and prepare focused pull requests.
Why use it?
It gives a team consistent ways to name changes, keep commits focused, and avoid unfinished or low-quality code entering shared branches.

Instructions file for Kiro

Written for Kiro: installed under .kiro/.

This is Huzaifa-ali/post-kit's own configuration. It tells Kiro how to work on post-kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything post-kit configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Huzaifa-ali/post-kit/master/.kiro/steering/git-workflow.md
Clone the repo
git clone --depth 1 https://github.com/Huzaifa-ali/post-kit

Made for: Kiro.

Wrote 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.

agentmods badge for post-kit git-workflow.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/git-workflow/github.svg)](https://agentmods.dev/instructions/huzaifa-ali/post-kit/git-workflow)
Your own site
<a href="https://agentmods.dev/instructions/huzaifa-ali/post-kit/git-workflow"><img src="https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/git-workflow/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.

agentmods 80×15 button for post-kit git-workflow.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/huzaifa-ali/post-kit/git-workflow"><img src="https://agentmods.dev/badge/instructions/huzaifa-ali/post-kit/git-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 304 This file is loaded in full into every session.
When invoked 304 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00304 $0.00304
Opus 5.5 $0.00122 $0.00122
Sonnet 5.5 $0.00061 $0.00061
Haiku 4.5 $0.00030 $0.00030

Measured 16d ago against content hash 7a072c0e5bf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

post-kit git-workflow.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.

.kiro/steering/git-workflow.md · 41 lines

What it actually says

Git & Contribution Standards

Branch Strategy

  • master — stable, merged PRs only
  • feat/web-ui — main development branch for the app
  • Feature branches off feat/web-ui for individual modules/features

Commit Messages

Format: <type>: <short description>

Types:

  • feat — new feature or module
  • fix — bug fix
  • refactor — code restructure without behavior change
  • docs — documentation only
  • style — formatting, no code logic change
  • test — adding or updating tests
  • chore — build, config, tooling changes

Examples:

  • feat: add library module with post listing and filters
  • fix: handle missing cadence field in niche.yaml gracefully
  • refactor: extract fetch utility from app.js

Keep subject under 72 characters. No period at end.

Code Quality

  • No commented-out code committed. Delete it — git has history.
  • No TODO or FIXME without a linked issue or clear explanation.
  • No debug prints/console.logs in committed code (use proper logging).
  • Every file must have a purpose. No empty files, no placeholder files beyond __init__.py.

PR Standards

  • One concern per PR. Don't mix refactoring with feature work.
  • PR description: what changed, why, how to test.
  • All steering rules must pass before merge.
Changes

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.

  1. 16d ago First seen · 41 lines · 304 tokens per session scan A 7a072c0e5bf9

Subscribe to this mod's changes

post-kit git-workflow.md is an instructions file published in the GitHub repository Huzaifa-ali/post-kit (4 stars, last pushed 17d ago), licensed MIT. It adds 304 tokens to every session, about $0.0012 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.

Related

Other instructions, from other repositories

skill-doctor github-automation.instructions.md

Instructions for evilstar2016/skill-doctor, covering github-automation, description, when to use and instructions.

evilstar2016/skill-doctor · 72 tokens

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens