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/jnzader/repoforge/generationnpx skills add JNZader/repoforge --skill generationgit clone --depth 1 https://github.com/JNZader/repoforgeWrote 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/jnzader/repoforge/generation)<a href="https://agentmods.dev/skills/jnzader/repoforge/generation"><img src="https://agentmods.dev/badge/skills/jnzader/repoforge/generation.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.1 | $0.00030 | $0.00493 |
| Opus 5 | $0.00015 | $0.00246 |
| Sonnet 5 | $0.00006 | $0.00099 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
add-generation-event 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 5d 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.
What it actually says
add-generation-event
This skill covers the creation and management of Generation and GenerationEvent ORM models.
Trigger: When working with generation data in the backend.
Quick Reference
| Task | Pattern |
|---|---|
| Create a Generation | create-generation |
| Log a GenerationEvent | log-generation-event |
Critical Patterns (Summary)
- Create a Generation: Use the Generation model to create new generation records.
- Log a GenerationEvent: Utilize the GenerationEvent model to log events related to generations.
Critical Patterns (Detailed)
Create a Generation
This pattern demonstrates how to create a new Generation record using the Generation model.
from apps.server.app.models.generation import Generation
from uuid import uuid4
from datetime import datetime
new_generation = Generation(
id=uuid4(),
created_at=datetime.utcnow(),
updated_at=datetime.utcnow()
)
Log a GenerationEvent
This pattern shows how to log a GenerationEvent related to a specific Generation.
from apps.server.app.models.generation import GenerationEvent
from uuid import uuid4
from datetime import datetime
event = GenerationEvent(
id=uuid4(),
generation_id=new_generation.id,
event_time=datetime.utcnow(),
description="Generation created"
)
When to Use
- When you need to create a new generation record in the database.
- When logging events related to a specific generation for tracking purposes.
Commands
python -m apps.server.app.models.generation
Anti-Patterns
Don't: Create Generation without Validation
Creating a Generation without proper validation can lead to data integrity issues.
# BAD
new_generation = Generation(id=None) # Missing required fields
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.
- 5d ago First seen · 95 lines · 30 tokens per session scan A 037f38891f2c
add-generation-event is a skill published in the GitHub repository JNZader/repoforge (5 stars, last pushed 11d ago), licensed MIT. It adds 30 tokens to every session and 493 once invoked, about $0.0002 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
qdrant
Vector search engine for production RAG systems.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.
chroma
Embedding database for RAG and semantic search.
pinecone
Managed vector DB for production RAG and search.
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Django, TypeORM, golang-migrate). Use when planning or implementing database schema changes.
swift-actor-persistence
Thread-safe data persistence in Swift using actors — in-memory cache with file-backed storage, eliminating data races by design.