followups

followups is a cursor rule for Cursor from 567-labs/instructor. It costs 65 tokens per session, scanned A, original, MIT.

A rule that asks for small, useful follow-up code changes and assigns them to the hotkeys J, K, and L.

In plain words
What is it for?
Use it at the end of a coding task to suggest three actionable follow-ups based on the available project context.
Why use it?
It helps turn the current work into clear next actions instead of leaving possible improvements unspecified.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it at the end of a coding task to suggest three actionable follow-ups based on the available project context.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/567-labs/instructor/followups
About the project

Instructor is a library that helps applications obtain structured, validated data from language models using Pydantic models. It is for developers building LLM features such as data extraction across different model providers, and the catalogue entries add usage rules and instructions.

567-labs/instructor · 14,028 stars · on GitHub · python.useinstructor.com

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.

Clone the repo
git clone --depth 1 https://github.com/567-labs/instructor

Made for: Cursor.

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 followups

README.md
[![agentmods](https://agentmods.dev/badge/rules/567-labs/instructor/followups/github.svg)](https://agentmods.dev/rules/567-labs/instructor/followups)
Your own site
<a href="https://agentmods.dev/rules/567-labs/instructor/followups"><img src="https://agentmods.dev/badge/rules/567-labs/instructor/followups/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 followups

Your own site · 80×15
<a href="https://agentmods.dev/rules/567-labs/instructor/followups"><img src="https://agentmods.dev/badge/rules/567-labs/instructor/followups.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 This file is loaded in full into every session.
When invoked 65 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.00065 $0.00065
Opus 5.5 $0.00026 $0.00026
Sonnet 5.5 $0.00013 $0.00013
Haiku 4.5 $0.00006 $0.00006

Measured 1mo ago against content hash ed45ba690484, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

followups 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 1mo 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.

.cursor/rules/followups.mdc · 9 lines

What it actually says

Make sure to come up with follow-up hot keys. They should be thoughtful and actionable and result in small additional code changes based on the context that you have available.

using [J], [K], [L]

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. 1mo ago First seen · 9 lines · 65 tokens per session scan A ed45ba690484

Subscribe to this mod's changes

followups is a cursor rule published in the GitHub repository 567-labs/instructor (14,028 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session, about $0.0003 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-08-30.