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 fatihguner/foreman --skill shamrock-organisationgit clone --depth 1 https://github.com/fatihguner/foremanWrote 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/fatihguner/foreman/shamrock-organisation)<a href="https://agentmods.dev/skills/fatihguner/foreman/shamrock-organisation"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/shamrock-organisation/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/fatihguner/foreman/shamrock-organisation"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/shamrock-organisation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.02825 |
| Opus 5 | $0.00040 | $0.01412 |
| Sonnet 5 | $0.00016 | $0.00565 |
| Haiku 4.5 | $0.00008 | $0.00282 |
Grade A, and why
shamrock-organisation 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 6d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.
The Shamrock Organisation
By 2030, the majority of the global workforce will not hold traditional full-time employment. This is not speculation -- it is the arithmetic consequence of trends already visible in labour statistics across every developed economy. Charles Handy saw it coming in 1989. His model of the Shamrock Organisation, articulated in The Age of Unreason, described a workforce structure built on three distinct leaves: a professional core, an outsourced contractual fringe, and a flexible labour force. What seemed provocative in the late twentieth century now reads as operational reality for any startup that has ever hired a freelance designer, contracted a development agency, or employed gig workers for delivery logistics.
The framework matters for entrepreneurs not as theory but as architecture. How you compose your workforce determines your cost structure, your agility, your culture, and ultimately your capacity to scale. Get the shamrock wrong, and you either bloat with fixed costs or hollow out the capabilities that make your company distinctive.
The Framework
Leaf One: The Professional Core
These are the indispensable people -- the ones who carry the organisation's institutional knowledge, strategic direction, and proprietary capability. They are expensive, difficult to replace, and worth every unit of compensation.
Characteristics:
- Full-time, salaried, deeply embedded in company culture
- Possess knowledge that cannot be easily codified or transferred
- Their departure would create genuine strategic damage
- Compensated through salary, equity, career development, and purpose
The entrepreneur's question: Which roles, if vacated tomorrow, would threaten the company's survival or competitive advantage? Those belong in the core. Everything else is a candidate for the other two leaves.
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.
- 6d ago First seen · 195 lines · 80 tokens per session scan A 6a71204863b2
shamrock-organisation is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 7d ago), licensed MIT. It adds 80 tokens to every session and 2,825 once invoked, about $0.0004 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-09-06.
Other skills, from other repositories
manage-taskboard
Manage Codex Taskboard / e-taskboard work with taskctl. Use for taskboard issue IDs, status sync, comments, or taskctl cloud setup—not for unrelated product docs.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
fly
Fly one thought to its destination across concurrent agents, on whatever the project and harness already have. Lands only when the user has accounted for every detail, never on an agent's say-so.
plan-to-issues
A tool that turns an agreed work plan into linked GitHub issues, with one larger parent issue and smaller task issues beneath it.
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…