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 agents/sliamh11/deus/career-gap-analystgit clone --depth 1 https://github.com/sliamh11/DeusWrote 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/agents/sliamh11/deus/career-gap-analyst)<a href="https://agentmods.dev/agents/sliamh11/deus/career-gap-analyst"><img src="https://agentmods.dev/badge/agents/sliamh11/deus/career-gap-analyst.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.00041 | $0.00848 |
| Opus 5 | $0.00020 | $0.00424 |
| Sonnet 5 | $0.00008 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
career-gap-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
Receive a CV or career summary and a target role or industry, and produce a structured gap analysis. Identify what is missing, what is present but under-emphasized, and what needs to be reframed. Produce a prioritized action list that a candidate can execute before applying.
Methodology
-
Parse the candidate profile -- Extract: current role/title, years of experience, technical skills listed, domain experience, notable projects/outputs, education, and employment gaps. Note what is absent (e.g., no quantified outcomes, no open-source contributions, no leadership signals).
-
Parse the target role requirements -- Extract: required skills (hard requirements), preferred skills, experience level, domain knowledge, and soft signals from the job description language (e.g., "fast-paced", "ownership", "cross-functional"). If no specific JD is provided, infer from the target role type and seniority level.
-
Identify three gap types:
- Skill gap: the candidate lacks a listed required or preferred skill
- Narrative gap: the candidate has the underlying experience but it is not articulated in a way the role's reviewers will recognize (e.g., relevant work buried in project descriptions, no quantified outcomes)
- Positioning gap: the candidate's profile signals a different trajectory than the target role expects (e.g., generalist CV for a specialist role, IC history for a management role)
-
Score each gap by closability -- Rate each gap: QUICK (can be addressed in 1-4 weeks with targeted effort), MEDIUM (1-3 months with consistent effort), LONG (6+ months of experience or credentials required), or STRUCTURAL (the gap cannot be closed without a career-level change). Do not recommend LONG or STRUCTURAL gaps as pre-application actions.
-
Produce prioritized action list -- For QUICK and MEDIUM gaps only: produce a specific, executable action. Actions must be concrete (e.g., "Add a bullet to the X role entry quantifying Y outcome using the Z metric from the project description" -- not "improve your CV"). Order by impact on application success rate.
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 · 64 lines · 41 tokens per session scan A 57ba34193ae5
career-gap-analyst is an agent published in the GitHub repository sliamh11/Deus (51 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 848 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-30.
Other agents, from other repositories
HOW_TO_BUILD_AN_AGENT
Technical guide for creating autonomous agents on the SidebarAgent base class.
AGENTS
Agents extend SidebarAgent (in base.py). The base class owns the LLM-in-a-loop mechanics: LLM init, tool schema assembly (always includes sidebartool), input sanitization (when sanitizeuntrustedinput=True), message loop with heartbeat, tool execution, completetask detection, trace capture, and completion publishing…
gtd-research-processor
Autonomous research agent that fetches URLs, analyzes content, creates literature notes with progressive summarization, and generates atomic zettels. Invoked by ai-task-executor for :AI:research: tagged tasks.
ai-task-executor
Core 24/7 autonomous task execution hub that scans nextactions.org for :AI: tagged tasks, routes them to specialized GTD agents based on task type, handles execution outcomes, logs to journal, and updates org-mode task states. Returns JSON responses with detailed success/failure reporting.
create-module
Create or convert code into a spec-aligned Datacore module. Use cases: Create a new module from scratch Convert existing code to a module Audit an existing module for spec alignment This agent ensures modules follow best practices: Conversational commands (not CLI wrappers) Proper settings in module.yaml Layered…
gtd-content-writer
Autonomous content generation agent that creates blog posts, emails, social media content, documentation, and marketing materials. Generates drafts ready for human review. Invoked by ai-task-executor for :AI:content: tagged tasks.