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/benja-pauls/serpentstack/scaffoldnpx skills add Benja-Pauls/SerpentStack --skill scaffoldgit clone --depth 1 https://github.com/Benja-Pauls/SerpentStackWrote 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/skills/benja-pauls/serpentstack/scaffold)<a href="https://agentmods.dev/skills/benja-pauls/serpentstack/scaffold"><img src="https://agentmods.dev/badge/skills/benja-pauls/serpentstack/scaffold.svg" alt="Measured on agentmods" 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 | $0.00063 | $0.03337 |
| Opus 5 | $0.00032 | $0.01669 |
| Sonnet 5 | $0.00013 | $0.00667 |
| Haiku 4.5 | $0.00006 | $0.00334 |
Grade A, and why
scaffold 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 3d 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 — 401 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold
Generate boilerplate for new API endpoints and frontend pages in SerpentStack.
Adding a New API Endpoint
Given a resource name (e.g., projects), create the following files in order.
1. SQLAlchemy Model -- backend/app/models/{name}.py
Inherit from Base which provides id (UUID), created_at, and updated_at automatically.
import uuid
from sqlalchemy import Boolean, ForeignKey, String, Text
from sqlalchemy.dialects.postgresql import UUID
from sqlalchemy.orm import Mapped, mapped_column
from app.models.base import Base
class {Name}(Base):
__tablename__ = "{name}s"
title: Mapped[str] = mapped_column(String(255), nullable=False)
description: Mapped[str | None] = mapped_column(Text, nullable=True)
is_active: Mapped[bool] = mapped_column(Boolean, default=True)
# Owner — see Item model for the reference pattern
user_id: Mapped[uuid.UUID | None] = mapped_column(
UUID(as_uuid=True),
ForeignKey("users.id", ondelete="CASCADE"),
nullable=True,
index=True,
)
Register the model by adding to backend/app/models/__init__.py:
from app.models.{name} import {Name}
2. Pydantic Schemas -- backend/app/schemas/{name}.py
from datetime import datetime
from uuid import UUID
from pydantic import BaseModel
class {Name}Base(BaseModel):
title: str
description: str | None = None
class {Name}Create({Name}Base):
pass
class {Name}Update(BaseModel):
title: str | None = None
description: str | None = None
class {Name}Response({Name}Base):
id: UUID
is_active: bool
user_id: UUID | None
created_at: datetime
updated_at: datetime
model_config = {"from_attributes": True}
class {Name}ListResponse(BaseModel):
{name}s: list[{Name}Response]
total: int
skip: int
limit: int
3. Service Layer -- backend/app/services/{name}.py
Uses async SQLAlchemy sessions. Services return None or domain values — they never raise HTTPException. Services flush but do not commit — the route layer owns the transaction boundary. This allows multiple service calls to be composed in a single transaction.
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.
- 3d ago First seen · 401 lines · 63 tokens per session scan A 077e5982ae7a
scaffold is a skill published in the GitHub repository Benja-Pauls/SerpentStack (2 stars, last pushed 5mo ago), licensed MIT. It adds 63 tokens to every session and 3,337 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-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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…