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 skills add OutlineDriven/outline-driven-development --skill eligibility-batch-organizergit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/eligibility-batch-organizer)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/eligibility-batch-organizer"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/eligibility-batch-organizer/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/outlinedriven/outline-driven-development/eligibility-batch-organizer"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/eligibility-batch-organizer.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.00032 | $0.00753 |
| Opus 5.5 | $0.00013 | $0.00301 |
| Sonnet 5.5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
eligibility-batch-organizer 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- eligibility-batch-organizer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eligibility batch organizer
Contract
| Field | Bound contract |
|---|---|
| Trigger | User asks to classify projects against eligibility rules and create hierarchical child documents from a work summary. |
| Authority | Human-gated: requires explicit human confirmation before creating any child document; every other write is reversible local, with version control as the rollback. |
| Side effect | Creates one child document per eligible project under the specified parent, using the provided template. |
| Done | Child documents created per eligible project and partial failures reported. |
Inputs
- Work summary (required): a document that contains one or more project descriptions or entries.
- Project template (required): the page template to apply to each child project summary. May be embedded, referenced by ID, or provided inline.
- Target parent ID (required): the identifier of the parent document under which child pages are created.
- Eligibility criteria (required): explicit list of criteria used to classify a project as eligible. No defaults are applied; every criterion must be supplied.
- API credentials (required): valid credentials with create permissions on the target parent document.
Procedure
- Validate inputs. Confirm every required input is present and non-empty. Halt if any is missing. Done when: every required input is confirmed present, or a missing field is named.
- Parse the work summary. Extract every project entry. Treat each entry as a candidate. Done when: every project entry is extracted, or zero projects found is reported.
- Classify each project against the provided eligibility criteria as eligible or not. Produce a list of eligible projects with the matching criteria noted per project. Done when: the eligible list is produced, or zero eligible projects is reported.
- Present the preview list to the human: every project with its eligibility classification and the criteria that matched or did not match. Wait for explicit human confirmation. Done when: the human confirms, or authority is withheld and the skill stops.
- Upon confirmation, sequentially create one child document per eligible project under the target parent using the project template. Populate the template fields from the work summary entry. If any individual creation fails, record the failure by project name and continue with the remaining projects. Do not retry failed creations. Done when: every eligible project has a child document or a recorded failure.
- Report completion. List every child document that was created successfully, every project that failed, and the total count. Done when: the report lists successes, failures, and totals.
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.
- 1mo ago First seen · 47 lines · 32 tokens per session scan A eb8ef0438ea1
eligibility-batch-organizer is a skill published in the GitHub repository OutlineDriven/outline-driven-development (54 stars, last pushed 26d ago), licensed Apache-2.0. It adds 32 tokens to every session and 753 once invoked, about $0.0001 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-09-13.
Other skills, from other repositories
eligibility-batch-organizer
Use when the user asks to classify a batch of projects against eligibility rules and generate an approval preview before creating hierarchical child documents.
recipe-create-doc-from-template
Copy a Google Docs template, fill in content, and share with collaborators.
sred-project-organizer
Take a list of projects and their related documentation, and organize them into the SRED format for submission.
aidlc-outcomes-pack
Generate a comprehensive handover document at workflow close so the team can own, operate, and continue the system without re-running the workflow. Stage/phase/learning counts come from {{INVOKE}} engine runtime summary; prose comes from the artefacts. Writes OUTCOMES.md but never mutates workflow state or emits audit…
client-workspace
Create client folder structure in Drive, share docs, check permissions before calls.
setup-repo-skills
Use when the user wants one-time repository setup for tracker, triage labels, and domain conventions. Not for ongoing triage, issue creation, or multi-repo setup.