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/sma1lboy/coforce-apply/coforcenpx skills add Sma1lboy/coforce-apply --skill coforcegit clone --depth 1 https://github.com/Sma1lboy/coforce-applyWrote 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/sma1lboy/coforce-apply/coforce)<a href="https://agentmods.dev/skills/sma1lboy/coforce-apply/coforce"><img src="https://agentmods.dev/badge/skills/sma1lboy/coforce-apply/coforce.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.00129 | $0.01144 |
| Opus 5 | $0.00064 | $0.00572 |
| Sonnet 5 | $0.00026 | $0.00229 |
| Haiku 4.5 | $0.00013 | $0.00114 |
Grade A, and why
coforce 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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CoForce — entry point & router
CoForce Apply is a skill-first job application agent. This skill is the front door: it never does the work itself — it decides which skill should, then invokes it. It ships with the skill set, so routing works whether the user runs from a repo checkout (where AGENTS.md/CLAUDE.md carry the same table) or installed only the skills.
Route by intent
First action for a matched intent is invoking that skill — never answer ad hoc or improvise the workflow inline.
| The user is talking about… | Go to |
|---|---|
| First run, onboarding, 初始化, "set me up", missing data-home files | setup |
| Changing job-search preferences (level, directions, H1B/sponsorship, work mode, locations, salary) | setup (stage 2 only) or the console Settings tab |
| Their background: work history, projects, education, skills, awards/honors, certificates, "add X to my resume/record" | profile (Supplement flow takes raw material — a story, a link, a PDF) |
| Turning a GitHub URL / local repo into evidence or resume bullets | experience (Module 1: index + STAR bullets) |
| "Run a cycle", "find new jobs", "start hunting", recurring discovery | start |
| A batch of resumes for tracked jobs; reviewing/approving generated PDFs; ZIP export | campaign |
| One specific JD → one tailored resume (no tracker involvement) | tailor |
| Trying the product out, "does this work for me", first taste with nothing set up | tailor — deliver a PDF first, offer setup after |
| Submitting an application to a posting URL | apply |
| "Where are my applications", board, statuses, notes, archives | tracker |
| A scheduled interview: prep pack, mock interview, "帮我准备面试" | interview |
| "Why am I not getting callbacks", "该学什么", skill-gap retro | tracker (Retro — aggregates outcomes + campaign gap reports) |
| "Is this working", which bullets/resumes actually get callbacks | campaign (outcomes — counts, not evidence; pass its caveat on) |
Route by state (when the intent is vague)
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.
- 4d ago First seen · 72 lines · 129 tokens per session scan A 0d9ee97d597d
coforce is a skill published in the GitHub repository Sma1lboy/coforce-apply (5 stars, last pushed 5d ago), licensed MIT. It adds 129 tokens to every session and 1,144 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…