Borrowing it
Nothing to install: this file belongs to Sma1lboy/coforce-apply. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Sma1lboy/coforce-apply/main/.agents/skills/tailor/SKILL.mdgit 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/tailor)<a href="https://agentmods.dev/skills/sma1lboy/coforce-apply/tailor"><img src="https://agentmods.dev/badge/skills/sma1lboy/coforce-apply/tailor/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/sma1lboy/coforce-apply/tailor"><img src="https://agentmods.dev/badge/skills/sma1lboy/coforce-apply/tailor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.02230 |
| Opus 5.5 | $0.00000 | $0.00892 |
| Sonnet 5.5 | $0.00000 | $0.00446 |
| Haiku 4.5 | $0.00000 | $0.00223 |
Grade A, and why
tailor 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 2mo 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tailor — JD → resume
Input: a job description (URL to fetch, file path, or pasted text), optionally a
format ("docx", "pdf", "tex") and/or a template/reference file.
Read ~/.coforce/instructions.md first if present — standing user preferences
(tone, emphasis, format defaults) override this skill's defaults.
Profile source: ~/.coforce/profile.json.
No profile yet? Do not send the user to onboarding. This skill is the
product's front door: a stranger with one job posting should hold a tailored
PDF before being asked to invest in anything. Ask for an existing resume — a
PDF path, or text pasted straight into the conversation — parse it into
~/.coforce/profile.json following the profile skill's schema and its
import rules (bullets verbatim, nothing invented; a profile imported from the
user's own resume already counts as reviewed), then continue with the JD.
Two questions, not twenty. Mention /setup only AFTER delivering the PDF, and
only as what it adds: repeat cycles, job discovery, tracking, submission. The
profile skill's intake review of the resume they handed over belongs in that
same "after" — three lines on what a screener sees, once the PDF is in hand.
Nothing goes in front of the PDF.
When invoked by the campaign skill for a campaign job ID, the campaign
contract wins: read that job's saved JD/match/feedback, use the
latexTemplate from ~/.coforce/config.json, write resume.tex and
resume.pdf into that job's existing campaign folder, and leave approval to
the Review tab. Do not also write a duplicate resume under ~/.coforce/out/.
Template / reference resolution (first match wins)
- A file the user names explicitly.
- Files in
~/.coforce/templates/(may carry personal style or data). If several, ask once which to use. - Default:
assets/resume_template.texinside this skill's base directory — Jake's-resume style (letterpaper 11pt,\resumeSubheadingmacros, section order Education → Skills → Working Experience → Projects). Keep its macros and spacing intact; only fill the placeholder slots. Bullets take two arguments —\resumeItem{}{<bullet>}, the first being an optional bold label — and so does\resumeSubItem{<label>:}{<values>}in Skills. The campaign path shares this template and machine-checks that shape, so the one-argument form silently fails to compile.
What ships with it
1 file 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.
- 2mo ago First seen · 145 lines · 0 tokens per session scan A 89ce4cacdf5a
tailor is a skill published in the GitHub repository Sma1lboy/coforce-apply (5 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,230 tokens. 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.