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/qarium/goga/goga-cell-javascriptnpx skills add qarium/goga --skill goga-cell-javascriptgit clone --depth 1 https://github.com/qarium/gogaWhat 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.00014 | $0.00829 |
| Opus 5 | $0.00007 | $0.00415 |
| Sonnet 5 | $0.00003 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
goga-cell-javascript 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.
How it starts
The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JavaScript: Contract Implementation Rules
Language skill for JavaScript.
Apply the specification within the context of the invoking skill. Do not paraphrase the contents — use them to drive implementation decisions.
Invoked via the goga-lang-disp router.
Examples
Complete CODEMANIFEST example for JavaScript covering all DSL constructs:
Imports:
- Types:
- EventEmitter
- TransportConfig AS Config
Usages:
- retry_policy
From: path/to/events_cell
Usages:
conventions: .goga/usages/js_conventions.md
pattern: |
Use async/await for all asynchronous operations. Avoid callbacks.
testing: |
Use Jest. Each exported function and class method must have test coverage.
Annotations: |
Use `conventions` for code style.
Use `testing` for test requirements.
Use `retry_policy` from Imports for retry logic on transient failures.
All async functions must return `Promise<T>`.
---
"parseInput(input: string) -> data: Uint8Array":
location: parser.js
annotations: |
Parse raw input string into structured data.
`input`: raw string to parse
Use `pattern` for implementation.
"ApiClient(baseURL: string)":
location: api.js
annotations: |
HTTP client for external API communication.
`baseURL`: root URL for all API requests
Use `retry_policy` from Imports for request retries.
Use `conventions` for code style.
properties:
"baseURL -> string": |
Root URL for API requests.
"timeout -> number": |
Request timeout in milliseconds.
methods:
"fetchData(endpoint: string) -> response: Promise<Object<string, any>>": |
Fetch data from the specified endpoint.
`endpoint`: API endpoint path
`response`: async response data
Use `pattern` for implementation.
"close()": |
Close client and release resources.
"EventEmitter::SocketEmitter(url: string)":
location: emitter.js
annotations: |
Socket-based emitter extending EventEmitter with real-time capabilities.
`url`: WebSocket server URL
Use `retry_policy` from Imports for reconnection logic.
->EventEmitter: {}
---
Author: Goga
CreatedAt: 22/05/26
Description: |
Example CODEMANIFEST demonstrating all DSL constructs for JavaScript.
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 · 153 lines · 14 tokens per session scan A 793c11b57f2f
goga-cell-javascript is a skill published in the GitHub repository qarium/goga (13 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 14 tokens to every session and 829 once invoked, about $0.0001 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
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
ship-it
Worktree-side implementation orchestrator for an OpenSpec change. Idempotent: gates automated scenarios on filesystem reality, owns the red-test fix loop, runs the docker harness with always-teardown, then drives ship-change inline. Escape hatch writes SHIPITBLOCKED.md. Runnable headless. Triggers: "ship it", "build…
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
session-to-guideline
Turn a pi session into a Markdown "how-we-did-it" collaboration guideline: reads the session's JSONL transcript and synthesizes a reusable playbook of which prompts worked, what had to be steered, and how to reproduce the result faster. Use when: "document this session", "write up how we did X with the AI", "make a…
scenario-design
Draft real-life test SCENARIOS (not smoke tests) from a change/feature spec. Derives edge-case, performance, frontend-quirk and error-handling scenarios with ISTQB techniques, routes each to a test level, and writes test-plan.md, emitting clarification questions on a spec gap. Use on "design test scenarios", "what…