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.
npx skills add fatihguner/foreman --skill grow-modelgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/skills/fatihguner/foreman/grow-model)<a href="https://agentmods.dev/skills/fatihguner/foreman/grow-model"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/grow-model/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/skills/fatihguner/foreman/grow-model"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/grow-model.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.03781 |
| Opus 5 | $0.00044 | $0.01891 |
| Sonnet 5 | $0.00018 | $0.00756 |
| Haiku 4.5 | $0.00009 | $0.00378 |
Grade A, and why
grow-model 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 3d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
GROW Model
A gardener does not grow a plant. A gardener creates the conditions -- soil, light, water, space -- in which the plant grows itself. John Whitmore, the British racing driver turned executive coach, built the GROW model on precisely this philosophy of human development. Published in his 1992 book Coaching for Performance, GROW offers a deceptively simple four-stage questioning framework that has become the most widely used coaching structure in the world. Its power lies not in telling people what to do but in asking them questions that unlock their own clarity. For entrepreneurs, who chronically suffer from both advice overload and decision paralysis, GROW provides a structured pathway from muddled intention to committed action -- and, equally valuable, a repeatable method for coaching the people they lead.
The Framework
GROW is an acronym representing four sequential stages of a coaching conversation. Each stage has a distinct purpose and a characteristic set of questions. The coach (or self-coaching entrepreneur) moves through the stages in order, though real conversations often loop back as new insights emerge.
The Four Stages
G -- Goal
Establish what the person wants to achieve. Not vaguely ("I want to grow the business") but with specificity sufficient to recognise achievement. The goal stage separates wishful thinking from actionable intention.
Essential questions:
- What do you want to achieve?
- What would make this conversation most valuable for you?
- What does success look like? How would you know you had achieved it?
- What is the timeframe?
- How ambitious is this goal on a scale of 1-10?
- Is this a performance goal (within your control) or an end goal (dependent on external factors)?
The distinction between performance goals and end goals is critical for entrepreneurs. "Raise a Series A" is an end goal -- it depends on investor decisions outside the founder's control. "Complete 30 investor conversations and iterate the pitch to a 50% follow-up rate" is a performance goal -- fully within the founder's control and far more useful for coaching.
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.
- 3d ago First seen · 235 lines · 89 tokens per session scan A 116932b27c3e
grow-model is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 3,781 once invoked, about $0.0004 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-06.
Other skills, from other repositories
manage-taskboard
Manage Codex Taskboard / e-taskboard work with taskctl. Use for taskboard issue IDs, status sync, comments, or taskctl cloud setup—not for unrelated product docs.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
people-ops
Use when the offer is signed and you now have to run the person — an onboarding plan from preboarding through the 30/60/90 ramp, drafting or auditing an internal policy or handbook section, standing up the recurring people rhythm (1:1s, review and goal cycles, headcount), or offboarding a leaver. NOT sourcing…
fly
Fly one thought to its destination across concurrent agents, on whatever the project and harness already have. Lands only when the user has accounted for every detail, never on an agent's say-so.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…