Borrowing it
Nothing to install: this file belongs to Dallionking/agent-goal-skill. 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/Dallionking/agent-goal-skill/main/AGENTS.mdgit clone --depth 1 https://github.com/Dallionking/agent-goal-skillWrote 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/dallionking/agent-goal-skill/agents-md)<a href="https://agentmods.dev/instructions/dallionking/agent-goal-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/dallionking/agent-goal-skill/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/dallionking/agent-goal-skill/agents-md"><img src="https://agentmods.dev/badge/instructions/dallionking/agent-goal-skill/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.00857 | $0.00857 |
| Opus 5.5 | $0.00343 | $0.00343 |
| Sonnet 5.5 | $0.00171 | $0.00171 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
agent-goal-skill 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.
This is a copy
83% identical to claude-code-trace AGENTS.md — 63 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitNexus — Code Intelligence
This project is indexed by GitNexus as agent-goal-skill (96 symbols, 95 relationships, 0 execution flows). Use the GitNexus MCP tools to understand code, assess impact, and navigate safely.
If any GitNexus tool warns the index is stale, run
npx gitnexus analyzein terminal first.
Task tracking & execution (Standard Workflow — 2026-07-12)
- Tasks live in Linear (workspace dallion-king, project Community Kits, team DAL); GitHub is the PR/code loop. New persistent task → Linear issue (wave-labeled).
- Builds run through Orca: pull the Linear task →
orca status→ orchestrator session (Fable/Claude side or Sol/Codex side per model lanes) →~/.local/bin/orca-dispatch-taskper task (worktree waves, depth-1 workers) → gates (Greptile review + Codex cross-model + coordinator) → PR → merge → cleanup per the ownership ledger. - Loop spec:
~/.claude/references/loop-registry.md(Core-5: BUILD, TICK+TIMER, CLEANUP, PR-SWEEP, GAP). Constitution:~/AGENTS.md.
Always Do
- MUST run impact analysis before editing any symbol. Before modifying a function, class, or method, run
gitnexus_impact({target: "symbolName", direction: "upstream"})and report the blast radius (direct callers, affected processes, risk level) to the user. - MUST run
gitnexus_detect_changes()before committing to verify your changes only affect expected symbols and execution flows. - MUST warn the user if impact analysis returns HIGH or CRITICAL risk before proceeding with edits.
- When exploring unfamiliar code, use
gitnexus_query({query: "concept"})to find execution flows instead of grepping. It returns process-grouped results ranked by relevance. - When you need full context on a specific symbol — callers, callees, which execution flows it participates in — use
gitnexus_context({name: "symbolName"}).
Never Do
- NEVER edit a function, class, or method without first running
gitnexus_impacton it. - NEVER ignore HIGH or CRITICAL risk warnings from impact analysis.
- NEVER rename symbols with find-and-replace — use
gitnexus_renamewhich understands the call graph. - NEVER commit changes without running
gitnexus_detect_changes()to check affected scope.
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 First seen · 48 lines · 857 tokens per session scan A 853c563020a0
agent-goal-skill AGENTS.md is an instructions file published in the GitHub repository Dallionking/agent-goal-skill (11 stars, last pushed 3mo ago), licensed MIT. It adds 857 tokens to every session, about $0.0034 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to claude-code-trace AGENTS.md, differing in 63 lines, and is treated as a copy.
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.