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 skills add wasintoh/toh-framework --skill backend-engineergit clone --depth 1 https://github.com/wasintoh/toh-frameworkWrote 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/wasintoh/toh-framework/backend-engineer)<a href="https://agentmods.dev/skills/wasintoh/toh-framework/backend-engineer"><img src="https://agentmods.dev/badge/skills/wasintoh/toh-framework/backend-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/wasintoh/toh-framework/backend-engineer"><img src="https://agentmods.dev/badge/skills/wasintoh/toh-framework/backend-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 46 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 65 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00075 | $0.03661 |
| Opus 5.5 | $0.00030 | $0.01464 |
| Sonnet 5.5 | $0.00015 | $0.00732 |
| Haiku 4.5 | $0.00007 | $0.00366 |
Grade A, and why
backend-engineer 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 1mo 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 — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer
Connect beautiful UI to real data. Supabase-first approach.
<core_principle>
The Integration Promise
Working UI with mock data → Connect Supabase → Real data flows automatically
We DON'T redesign. We DON'T add features. We connect what exists. </core_principle>
<default_to_action> NEVER ask:
- "Which database should I use?" → Supabase (our standard)
- "What's the schema?" → Derive from existing TypeScript types
- "What type of auth do you need?" → Supabase Auth with social providers
ALWAYS do:
- Create Supabase client configuration
- Generate schema from existing types
- Setup RLS policies
- Replace mock API calls with Supabase queries </default_to_action>
<supabase_setup>
Initial Setup
1. Install Dependencies
npm install @supabase/supabase-js
2. Environment Variables
# .env.local
NEXT_PUBLIC_SUPABASE_URL=https://xxxxx.supabase.co
NEXT_PUBLIC_SUPABASE_ANON_KEY=eyJhbGc...
3. Client Configuration
// src/lib/supabase.ts
import { createClient } from '@supabase/supabase-js'
import { Database } from '@/types/supabase'
const supabaseUrl = process.env.NEXT_PUBLIC_SUPABASE_URL!
const supabaseKey = process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!
export const supabase = createClient<Database>(supabaseUrl, supabaseKey)
4. Type Generation (after creating tables)
npx supabase gen types typescript --project-id xxxxx > src/types/supabase.ts
</supabase_setup>
<schema_patterns>
Database Schema Patterns
Derive from TypeScript Types
// Existing type from dev-engineer
interface Product {
id: string
name: string
description: string
price: number
stock: number
category: string
isActive: boolean
createdAt: Date
updatedAt: Date
}
// Becomes SQL
-- SQL for Supabase
create table products (
id uuid default gen_random_uuid() primary key,
name text not null,
description text,
price decimal(10,2) not null default 0,
stock integer not null default 0,
category text not null,
is_active boolean not null default true,
created_at timestamp with time zone default now(),
updated_at timestamp with time zone default now()
);
-- Auto-update updated_at
create or replace function update_updated_at()
returns trigger as $$
begin
new.updated_at = now();
return new;
end;
$$ language plpgsql;
create trigger products_updated_at
before update on products
for each row execute function update_updated_at();
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.
- 1mo ago First seen · 617 lines · 75 tokens per session scan A bca4448d605e
backend-engineer is a skill published in the GitHub repository wasintoh/toh-framework (98 stars, last pushed 1mo ago), licensed MIT. It adds 75 tokens to every session and 3,661 once invoked, about $0.0003 per session on Opus 5.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
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.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
event-sourcing-architect
Expert in event sourcing, CQRS, and event-driven architecture patterns. Masters event store design, projection building, saga orchestration, and eventual consistency patterns. Use PROACTIVELY for event-sourced systems, audit trails, or temporal queries.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
database-connections
Connect a Mendix app to an external database over JDBC with the External Database Connector, and define the queries microflows run against it. Use when the app must read or write Oracle, PostgreSQL, MySQL or SQL Server directly from a microflow.
connect-rapidminer-graph
Fetch data from a RapidMiner graph mart or any SPARQL 1.1 HTTP endpoint (AnzoGraph and friends) and surface it as Mendix entities. Use when a graph database with a SPARQL endpoint has to feed a Mendix app read-only.