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/dosco/graphjin/graphjin-env-workflowsnpx skills add dosco/graphjin --skill graphjin-env-workflowsgit clone --depth 1 https://github.com/dosco/graphjinWhat 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.00060 | $0.01139 |
| Opus 5 | $0.00030 | $0.00570 |
| Sonnet 5 | $0.00012 | $0.00228 |
| Haiku 4.5 | $0.00006 | $0.00114 |
Grade A, and why
graphjin-env-workflows 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 today.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GraphJin environment workflows (in this repo)
For working on GraphJin. Someone using a published environment wants the
graphjin-env skill instead, and the public documentation is at
https://graphjin.com/environment/.
Which loop are you in
| Goal | Entry point |
|---|---|
| Measure: does the agent still work | graphjin eval create → eval run / eval baseline |
| Collect: build a training corpus | graphjin eval sample → eval export |
| Serve: give a training loop an environment | graphjin env serve |
| Mint: get a world that is not the demo | graphjin env new-world / env clone |
They share one engine. A change to scoring, task semantics or provenance affects all four.
Gates
Run the ones your change touches, not just the fast one.
go build -o /dev/null ./cmd/ && go vet ./cmd/
go test ./cmd/ ./agent/... -count=1 # ~2 minutes
cd website && npm run build && npm run check # required for any website/** change
make env-image-smoke # skips cleanly without docker or ko
npm run check is the gate, not hugo. It validates every internal link and
anchor, pins load-bearing copy, and derives several assertions from Go source —
so a docs change can fail on a code file and vice versa.
Never hand-edit
eval/suite.yml,eval/suite.split.json,eval/authored.yml— useeval add/eval rm, which go through the validated writer. Task ids are content hashes; editing a prompt detaches the task from every stored episode.website/data/benchmarks/<slug>.yamlandwebsite/content/benchmarks/<slug>/runs/—graphjin eval publishis the only sanctioned writer.- Anything under
.graphjin-evals/.
Contracts that move fingerprints
Know before you edit, because these invalidate comparisons rather than break builds:
agent/skills.go— any string movesPromptRegistryHash(), which is recorded in run provenance. Every baseline comparison across that edit is invalid whether or not behaviour changed.- Skill payload budgets are test literals in
agent/skills_test.go, and they ratchet both ways. A guide gated behind agj_*root costs an ordinary caller nothing; universal guidance costs every caller. Bump a budget visibly in the diff rather than routing prose through an uncounted channel. eval.GeneratorVersion— bump when generated task semantics change, and append the previous literal toSupportedGeneratorVersions.RewardVersion— bump on any scoring change. Runs either side are not comparable.suiteIdentityProjection— a new field changes every existing run's identity unless it isomitemptyat its zero value.
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.
- today First seen · 101 lines · 60 tokens per session scan A 1aef6e3e21e4
graphjin-env-workflows is a skill published in the GitHub repository dosco/graphjin (3,157 stars, last pushed yesterday), licensed Apache-2.0. It adds 60 tokens to every session and 1,139 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-09-02.
Other skills, from other repositories
Database Schema Reviewer
Reviews database schemas for normalization issues, missing indexes, naming inconsistencies, and scalability risks.
sql-expert
Expert-level SQL database design, querying, optimization, and administration across PostgreSQL, MySQL, and SQL Server.
database-sql
Design database schemas, write efficient SQL queries, create migrations, and optimize database performance. Use when working with databases, writing queries, or designing data models.
database-query
Generate, optimize, and explain SQL queries - supports SQLite, PostgreSQL, MySQL with schema introspection, migration generation, and query performance analysis.
sql
SQL patterns for database querying and design.
database-query
Natural language database queries with multi-database support, query optimization, and visual results.