Borrowing it
Nothing to install: this file belongs to frostney/GocciaScript. 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/frostney/GocciaScript/main/AGENTS.mdgit clone --depth 1 https://github.com/frostney/GocciaScriptWrote 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/frostney/gocciascript/agents-md)<a href="https://agentmods.dev/instructions/frostney/gocciascript/agents-md"><img src="https://agentmods.dev/badge/instructions/frostney/gocciascript/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/frostney/gocciascript/agents-md"><img src="https://agentmods.dev/badge/instructions/frostney/gocciascript/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.01393 | $0.01393 |
| Opus 5.5 | $0.00557 | $0.00557 |
| Sonnet 5.5 | $0.00279 | $0.00279 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade A, and why
GocciaScript 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 5d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding assistants (Cursor, Claude Code, and similar) working in this repository.
Contributing guide vs this file
| Purpose | |
|---|---|
| CONTRIBUTING.md | Contributing guide for all contributors—humans and agents. Workflow, critical rules, testing, Pascal code style, formatting, build/run reference, documentation index. If it affects what may be merged, it belongs there. |
This file (AGENTS.md; CLAUDE.md imports it) |
Agent-only context: how assistants should operate in this repo, where to read first, and what not to duplicate. It does not replace CONTRIBUTING. |
Assistants should treat CONTRIBUTING as authoritative for contribution requirements. Use this file for assistant-specific expectations and navigation, not a second copy of CONTRIBUTING.
Expectations for assistants
- Follow the known-good-route operating loop for repository work. A defect in its skills or helpers is fixed upstream in known-good-route, not worked around here.
- Vendored vs repo-native skills: skills listed in
skills-lock.jsonare vendored by the skills CLI. Never hand-edit them; fix them upstream (known-good-route for its skills). Edit a repo-native skill (prepare-release,gocciascript-issue-validation,optimize-runtime,profile-report-review) only when the user asks to change that skill. - Infer architecture boundaries during planning: when a change touches website routes, API handlers, generated reports, external services, credentials, artifacts, caches, CI outputs, or deployment/build steps, identify where the work belongs (build time, request time, client time, CI/scheduled time) and compare against existing project patterns before implementing. Do not rely on the user or a skill checklist to spell this out.
- Search the real source layout: when prompts, automations, or audits search this repo, target
source/units,source/shared,source/app,tests,scripts, andwebsite/srcexplicitly. Do not assume a generic rootsrc/tree;source/generatedis generated data and should only be inspected or regenerated when the task specifically requires it. - Do source deep-dives before policy claims: follow the investigation discipline. For ECMAScript the normative source is ECMA-262/ECMA-402 (see TC39 spec lookup); classify each surface as shim-, parser-, runtime-, or object-model-level by the mechanism it needs.
- Cap memory for depth, fuzz and exponential probes: run them through
scripts/depth-probe.ts, which caps every probe process's memory and time, or wrap an ad-hoc run assystemd-run --user --scope -q -p MemoryMax=3G -p MemorySwapMax=0 -- timeout 120 <command>. Uncapped probes have grown a runner to 27 GB and set off the host's OOM killer. See Tooling — Depth and Fuzz Probe. - Clean first for stale FPC failures: after a merge, branch switch, PR sync,
generated resource change, or unexplained compiler/resource error, retry with
./build.pas --clean <target>(or./build.pas --clean) before diagnosing the reported source line. See Tooling — Stale FPC Build Artifacts.
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.
- 5d ago Changed · +1 tokens per session 9d8b671bcdd7
- 8d ago Changed · -27 tokens per session 134c6d48b697
- 11d ago Changed a52e3e696c82
- 20d ago Changed · +1 lines · +121 tokens per session 390ac399a462
- 25d ago Changed · -4 lines · -171 tokens per session 276cdc57490f
- 26d ago Changed · +2 lines · +66 tokens per session c328613e2fad
- 1mo ago Changed 280f58373d03
- 1mo ago Changed · +1 lines · +62 tokens per session 4ddc6f640630
- 1mo ago First seen · 67 lines · 1,341 tokens per session scan A 528ba8375535
GocciaScript AGENTS.md is an instructions file published in the GitHub repository frostney/GocciaScript (20 stars, last pushed yesterday), licensed MIT. It adds 1,393 tokens to every session, about $0.0056 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.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.