Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/leopu00/job-hunter-teamnpx agentmods add skills/leopu00/job-hunter-team/db-insertWrote 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/leopu00/job-hunter-team/db-insert)<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/db-insert"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/db-insert/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/leopu00/job-hunter-team/db-insert"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/db-insert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00938 |
| Opus 5.5 | $0.00027 | $0.00375 |
| Sonnet 5.5 | $0.00014 | $0.00188 |
| Haiku 4.5 | $0.00007 | $0.00094 |
Grade A, and why
db-insert 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
db-insert — record creation on the JHT DB
Wrapper at /app/shared/skills/db_insert.py. Creates new records in the JHT SQLite DB. Required fields differ per table.
Pattern
python3 /app/shared/skills/db_insert.py <table> --<field> <value> [--<field> <value>...]
Tables: position, company, score, application, highlight.
Position (Scout)
python3 /app/shared/skills/db_insert.py position \
--title "Python Developer" --company "Acme Corp" \
--location "Remote EU" --remote-type full_remote \
--url "https://acme.com/jobs/42" --source linkedin --found-by scout-1 \
--jd-text "<full JD text>" --requirements "Python, Flask, PostgreSQL"
--url is required (the script fails without it). The Scout must always pre-check duplicates with db-query check-url first.
Company (Analyst)
python3 /app/shared/skills/db_insert.py company \
--name "Acme Corp" --hq-country "Italy" --sector "fintech" \
--verdict GO --analyzed-by analista-1
--verdict accepts GO, CAUTIOUS, NO_GO.
Score (Scorer)
python3 /app/shared/skills/db_insert.py score \
--position-id 42 --total 85 \
--stack-match 35 --remote-fit 18 --salary-fit 8 \
--experience-fit 9 --strategic-fit 15 \
--scored-by scorer-1
The 5 sub-scores map to DB columns: stack_match · remote_fit · salary_fit · experience_fit · strategic_fit. --total is the canonical 0–100 score the Captain reads.
One score per call — write it immediately. The Scorer writes the score right after evaluating ONE position, then moves to the next. Never evaluate several positions and fire all the score inserts together at the end of the round: they would share the same scored_at second and look rushed. One position → one evaluation → one immediate insert → next (Scorer RULE-08).
Application (Writer)
python3 /app/shared/skills/db_insert.py application \
--position-id 42 \
--cv-path "/jht_user/applications/42/cv.md" \
--cv-pdf-path "/jht_user/applications/42/cv.pdf" \
--written-by scrittore-1 --written-at now
What ships with it
6 files 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.
- 1mo ago First seen · 90 lines · 68 tokens per session scan A 4fce2ab6f74e
db-insert is a skill published in the GitHub repository leopu00/job-hunter-team (52 stars, last pushed today), licensed MIT. It adds 68 tokens to every session and 938 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
x-osv
CLI for Google OSV database. Query vulnerabilities for packages, scan local projects for vulnerable dependencies. Dependency: This is an x-cmd module. Install x-cmd first (see x-cmd skill). Required Tool: Install osv-scanner for project scanning (see https://github.com/google/osv-scanner).
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
postgresdb
Use when PostgreSQL engine behaviour decides the answer — schema and type design, index choice, reading EXPLAIN on a slow query, zero-downtime DDL and backfills, or ops (roles, RLS, pooling, vacuum, partitioning, PITR). PG16, ORM-agnostic. NOT portable query logic (that is sql), NOT a managed provider's platform…
db-migrations
Use when a schema change must ship without downtime — NOT NULL, rename, type change, or backfilling millions of live rows — for the expand-contract sequence and the lock/batching discipline that keeps each step from freezing prod. NOT lock internals or EXPLAIN (that is postgresdb), NOT drizzle-kit mechanics (that is…
dynamodb
Use when modeling or operating a DynamoDB table: deriving partition/sort keys from access patterns, single-table vs table-per-entity, adding a GSI/LSI, on-demand vs provisioned capacity, or diagnosing hot-partition throttling. NOT relational schema/SQL/EXPLAIN (that is postgresdb), NOT aggregation-pipeline document…
firebase
Use when building on Firebase — Firestore data modeling, Security Rules, Auth and custom claims, Cloud Functions, Storage, modular Web/Admin SDK imports — including symptoms like a database open to the internet, a query rejected by rules, or a doc stuck at 1 write/sec. NOT managed-Postgres BaaS with SQL and RLS (that…