Borrowing it
Nothing to install: this file belongs to Aboudjem/goalify. 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/Aboudjem/goalify/main/AGENTS.mdgit clone --depth 1 https://github.com/Aboudjem/goalifyWrote 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/aboudjem/goalify/agents-md)<a href="https://agentmods.dev/instructions/aboudjem/goalify/agents-md"><img src="https://agentmods.dev/badge/instructions/aboudjem/goalify/agents-md/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/instructions/aboudjem/goalify/agents-md"><img src="https://agentmods.dev/badge/instructions/aboudjem/goalify/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02034 | $0.02034 |
| Opus 5.5 | $0.00814 | $0.00814 |
| Sonnet 5.5 | $0.00407 | $0.00407 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
goalify AGENTS.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 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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — goalify
Instructions for AI agents and coding assistants working in or invoking this repository. Plain
Markdown, no required fields (per the AGENTS.md convention: the agent parses the text below).
Human-facing docs live in README.md; this file holds the extra context an agent needs.
What this repo is
This repo is goalify, a Claude Code / Agent Skills skill that turns a big coding task into a
self-contained implementation brief plus the /goal completion condition derived from it. In one session it researches the task, locks the few real decisions
(asking the user only the genuine forks, one interactive MCQ batch), and authors two artifacts: a
self-contained implementation brief at an absolute path, and the condition string derived from
that brief's definition of done. The user then runs /clear and pastes the condition into /goal, so a
fresh session executes the big task at full context, proves every criterion in a closeout turn, and
archives the brief on success.
The repo is the skill at skills/goalify/SKILL.md, the /goalify author. goalify stays a skill
plugin: no MCP server, no standalone CLI, no runtime dependency, no network call. Its one
executable file, skills/goalify/scripts/condition_lint.py, is a standard-library helper the skill
may run over a condition before it prints the handoff. It is not a command users install and it
changes nothing about the output, which is still the brief plus the condition. /goal takes a condition string, never a file
path — the docs say "Run /goal followed by the condition you want satisfied" and the shipped
binary contains No goal set. Usage: /goal <condition> with no file-path branch. The evaluator behind
/goal has no tools and cannot read files, so a path handed to it can never be verified
(Claude Code 2.1.139+, https://code.claude.com/docs/en/goal).
How an agent should invoke / honor the skill
- If running inside Claude Code with the skill installed: trigger it by describing the user's intent,
e.g. "goalify this: ", "prep a goal", "make the brief for /goal", "set up an autonomous run to
launch later". Claude Code matches these to the skill's
descriptionand loadsSKILL.md. - Install: the plugin (
claude plugin marketplace add Aboudjem/10xthenclaude plugin install goalify@10x), or drop in manually:git clone https://github.com/Aboudjem/goalify, then copyskills/goalifyinto~/.claude/skills/. The runner is Claude Code's built-in/goal; goalify does not ship its own. - This skill AUTHORS a handoff file; it does not execute the task. If the user wants the work done
immediately in the current session, that is
autopilot/ultrawork/ralph, not goalify.
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.
- 1mo ago Changed · +7 lines · +148 tokens per session 686041fe8b5a
- 2mo ago First seen · 112 lines · 1,886 tokens per session scan A eabc5b520818
goalify AGENTS.md is an instructions file published in the GitHub repository Aboudjem/goalify (1 stars, last pushed 1mo ago), licensed MIT. It adds 2,034 tokens to every session, about $0.0081 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-31.
Other instructions, from other repositories
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).
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.
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).
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.