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/juanjitech/jframe/jframe-module-devnpx skills add juanjiTech/jframe --skill jframe-module-devgit clone --depth 1 https://github.com/juanjiTech/jframeWhat 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.00196 | $0.04574 |
| Opus 5 | $0.00098 | $0.02287 |
| Sonnet 5 | $0.00039 | $0.00915 |
| Haiku 4.5 | $0.00020 | $0.00457 |
Grade A, and why
jframe-module-dev scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **E2E**: `go build ./...` → `go vet ./...` → start server → curl endpoints How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jframe Module Development
This skill guides you through implementing the internal code of a jframe module — the handler, service, dao, and model layers, plus DI wiring, route registration, and testing.
Prerequisite: The module skeleton should already exist (created via jframe create -n <name> or manually). If not, use the jframe-module-design skill first — it walks through requirements gathering, lifecycle phase selection, config struct design, DI planning, scaffolding, and module registration.
Module internal architecture
jframe modules follow a layered architecture convention:
mod/<name>/
├── mod.go # Lifecycle entry point — DI wiring, route registration
├── handler/ # HTTP/gRPC request handling — parse input, call service, format response
├── service/ # Business logic — orchestrates dao calls, enforces rules
├── dao/ # Data access — GORM queries, wraps stdao
├── model/ # Data models — GORM structs, DTOs
└── e/ # Error codes — domain-specific error definitions
Data flow: handler → service → dao → model
The handler receives requests, calls service methods with domain types, the service implements business rules and calls dao for persistence, and the dao talks to the database through GORM. This separation keeps each layer testable and replaceable.
Implementing the model layer
Models define your data structures. For database-backed models, embed stdao.Model which provides ULID primary key, timestamps, and soft delete:
// mod/<name>/model/user.go
package model
import "github.com/juanjiTech/jframe/pkg/stdao"
type User struct {
stdao.Model
Username string `json:"username" gorm:"uniqueIndex;size:64"`
Email string `json:"email" gorm:"size:256"`
Status int `json:"status" gorm:"default:1"`
}
stdao.Model gives you:
type Model struct {
ID string `json:"id" gorm:"primaryKey;size:26"` // ULID
CreatedAt time.Time `json:"createdAt"`
UpdatedAt time.Time `json:"updatedAt"`
DeletedAt *gorm.DeletedAt `json:"deletedAt" gorm:"index"` // soft delete
}
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 · 493 lines · 196 tokens per session scan A 4fa192fd46f3
jframe-module-dev is a skill published in the GitHub repository juanjiTech/jframe (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 196 tokens to every session and 4,574 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.