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 agentmods add skills/frostney/gocciascript/native-nostalgia-stacknpx skills add frostney/GocciaScript --skill native-nostalgia-stackgit clone --depth 1 https://github.com/frostney/GocciaScriptWhat 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 | $0.00051 | $0.00630 |
| Opus 5 | $0.00026 | $0.00315 |
| Sonnet 5 | $0.00010 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
native-nostalgia-stack 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- native-nostalgia-stack — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native nostalgia stack
Apply only the contract material to the requested work. Project AGENTS and docs
own implementation rules and exact commands; project-structure/SKILL.md owns
language-neutral layout and documentation.
Compiler and layout
- Use the project-pinned latest stable FPC and Delphi mode unless project docs explicitly choose another mode.
- Keep project-wide compiler directives in one shared include used by every unit.
- Put Pascal source under one root (
source/preferred), using namespaced filenames and a flat layout until a namespace becomes unwieldy. - Co-locate unit tests; keep delivered end-to-end corpora under root
tests/. - Put all ignored build output under root
build/. - Prefer executable InstantFPC for one-off Pascal scripts; use an existing task runner or dynamic language only when that is materially simpler.
Read references/code-style.md when writing or reviewing Pascal source.
Build contract
The project chooses the implementation but provides one root entry point:
- bare invocation performs a clean development build of all binaries;
- positional names select one or more binary targets;
- development is the default and a production flag selects release settings;
cleanis a target and can be combined with a target;- every binary lands under
build/.
Document the entry point, targets, and flags in docs/build-system.md; read it
before changing them.
Formatter and health contracts
One formatter/linter command rewrites Pascal by default and has a non-mutating
--check mode that exits non-zero on deviation. Project-specific style lives in
the tool and docs/code-style.md, not scattered config.
The codebase-health gate reports located duplication, per-function cyclomatic
and cognitive complexity, sortable file health, and complexity-times-churn
hotspots. Thresholds and ignores live in one root config; breaches exit
non-zero. Document the tool and thresholds in docs/tooling.md.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 69 lines · 51 tokens per session scan A 798b136452d6
native-nostalgia-stack is a skill published in the GitHub repository frostney/GocciaScript (20 stars, last pushed 6d ago), licensed MIT. It adds 51 tokens to every session and 630 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
qcad
Use when editing DXF files with a professional open-source 2D CAD application — CAM output, part libraries, isometric projection. QCAD: open-source 2D CAD with DXF as native format, scriptable via ECMAScript.
oxc-docs
Comprehensive reference for the JavaScript Oxidation Compiler (Oxc) — a collection of high-performance JavaScript tools written in Rust. Covers parser design (lexer, AST, parser, errors, semantic analysis), architecture (parser, linter, test infrastructure, AST tools), ECMAScript specification and grammar, performance…
git-step-commit
Analyze Git changes, split them into coherent commits, infer message language and format, optionally close supplied GitHub issues, and execute safely. Manage persistent global or repository preferences for review versus direct submission and automatic or specified commit-message language through native Git config.…
manage-prd-docs
Automatically manage product requirements across current decisions in docs/PRD.md and docs/prd/, mature future plans under docs/plans/, and active implementation under docs/work/. Use whenever the conversation discusses, clarifies, versions, plans, implements, completes, splits, or migrates a product requirement or…
modernize-ecmascript
当 Agent 编写或修改 JavaScript、TypeScript，用户要求按指定环境、输出版本、ES20xx 或具体语法编写代码，询问某项 ECMAScript 语法、标准内置 API 或提案能否采用，或者要求审查仓库中可简化、可现代化的写法时，应使用本 Skill。围绕目标文件真实经过的解析器、转换器和输出目标判断新语法能否安全采用，并按需读取 TC39 Atlas 的提案阶段、官方仓库、polyfill 与实现线索。.
codebase-audit
Audits the current repository for systemic correctness, architecture, churn, simplification, clarity, test value, and operational risks using current source and reproducible probes. It can delegate evidence gathering across bounded capability and perspective lanes. Use when the user runs /codebase-audit or asks for an…