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/spinningrachel/career-engine/databasenpx skills add spinningrachel/career-engine --skill databasegit clone --depth 1 https://github.com/spinningrachel/career-engineWrote 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/spinningrachel/career-engine/database)<a href="https://agentmods.dev/skills/spinningrachel/career-engine/database"><img src="https://agentmods.dev/badge/skills/spinningrachel/career-engine/database.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.00098 | $0.02673 |
| Opus 5 | $0.00049 | $0.01337 |
| Sonnet 5 | $0.00020 | $0.00535 |
| Haiku 4.5 | $0.00010 | $0.00267 |
Grade A, and why
database 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database — Pipeline Concepts
Backend-neutral vocabulary for the job applications tracker. Any database backend implements the same concepts here. Field names, tool calls, and query mechanics are backend-specific — see the adapter skill for those.
Backend adapters:
- Notion (default):
skills/database-notion/SKILL.md— read ladder, view discovery, writeback syntax, schema
Status Values
Status is the single property that drives what the pipeline does with a role. The user sets and updates it; agents update it at pipeline completion only.
| Status | Who sets it | Meaning |
|---|---|---|
New |
user (manual add, or any future sourcing pipeline) | True entry point — where a role sits immediately after being added, before Prioritization has touched it. Not yet triaged: no JD fetch, no location read, no priority score. This is what the Prioritization pipeline fetches by default. |
Needs Research |
user, or Prioritization pipeline (on completion) | Being researched before a decision to apply. NOT handled by the CV-writing pipeline. Use the intake pipeline (--coach-skills) to research Needs Research roles. That pipeline runs the career coach, writes strategic properties, and promotes Needs Research roles to Researched. (Renamed from Hold — same meaning, same trigger, purely a label change.) |
Interested |
user | The user has decided to apply. This is what the New Application pipeline fetches. Move a role from Needs Research → Interested (or add directly as Interested) when a CV and cover letter need to be produced. Intake does not process Interested roles — it only processes Needs Research roles. |
Needs editing |
user | Queued for the editing pipeline. Pipeline starts from existing outputs — does not run fresh. |
CV Ready for Review |
pipeline (on completion) | Pipeline finished; the user needs to review before sending. |
Applied |
user | Sent. |
Researched |
intake pipeline (on completion) | Coach has run market intelligence — competitive landscape, priority scoring, strategic properties. Role is ready for the user to decide whether to move to Interested. |
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 · 95 lines · 0 tokens per session scan A c89a29cf6095
database is a skill published in the GitHub repository spinningrachel/career-engine (4 stars, last pushed 22d ago), licensed MIT. It adds 98 tokens to every session and 2,673 once invoked, about $0.0005 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.