A project feedback command that records a framework improvement request and prepares a GitHub issue for the OpenStart project. It shows the local log and issue text before asking whether to file it.

Use it to capture an enhancement or other framework suggestion, optionally label its type and area, review the generated text, and then file it if approved.

It keeps feedback in the project's required format and prevents an issue from being sent without confirmation. The local record is written first.

feedback — Command by vijayatechlabs

Install

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.

agentmods

npx agentmods add commands/vijayatechlabs/openstart/feedback

Clone the repo

git clone --depth 1 https://github.com/vijayatechlabs/openstart

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 373 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00018	$0.00373
Opus 5	$0.00009	$0.00187
Sonnet 5	$0.00004	$0.00075
Haiku 4.5	$0.00002	$0.00037

Measured 2d ago against content hash 53821dde0d2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

feedback 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 2d 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.

.claude/commands/feedback.md · 37 lines

What it actually says

You are running the OpenStart feedback flow for the current project.

Follow .ai/framework/FEEDBACK.md exactly. It is the canonical description of the feedback pipeline.

Steps

Run the capture script with the user's message, type, and area:
```
bash .ai/framework/feedback.sh "<message>" [--type enhancement] [--area onboard]
```
Pass any --type or --area flags the user provided. If not provided, omit them (the script defaults to enhancement / general).
Show the output — the local log path and the full issue text — so the user can review both before anything goes to GitHub.
Ask for confirmation before filing. Do NOT run gh issue create automatically. External writes require explicit user confirmation (see AGENT-GUIDE.md §9 guardrails). Ask:

"Shall I file this as a GitHub issue on vijayatechlabs/openstart?"
If confirmed, run the gh issue create one-liner that feedback.sh printed and report the returned issue URL.

Non-negotiable rules

Never edit .ai/framework/ files to patch a framework gap — file feedback instead.
The local log (.ai/docs/FRAMEWORK-FEEDBACK.md) is always written first; GitHub filing is secondary and requires confirmation.
If feedback.sh exits non-zero (empty message, missing file), report the error and ask the user to supply the missing information.

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.

2d ago First seen · 37 lines · 18 tokens per session scan A 53821dde0d2d

Subscribe to this mod's changes

feedback is a command published in the GitHub repository vijayatechlabs/openstart (5 stars, last pushed 3d ago), licensed MIT. It adds 18 tokens to every session and 373 once invoked, about $0.0001 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-08-31.

Code review aeo

feedback

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Steps

Non-negotiable rules

What this file has done since we first saw it

Other commands, from other repositories

seo-audit

content-engine

performance-report

backlink-gap

seo-drift

geo