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.
git 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/commands/fatihguner/foreman/org-politics-commands)<a href="https://agentmods.dev/commands/fatihguner/foreman/org-politics-commands"><img src="https://agentmods.dev/badge/commands/fatihguner/foreman/org-politics-commands/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/commands/fatihguner/foreman/org-politics-commands"><img src="https://agentmods.dev/badge/commands/fatihguner/foreman/org-politics-commands.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.00056 | $0.00975 |
| Opus 5 | $0.00028 | $0.00487 |
| Sonnet 5 | $0.00011 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00097 |
Grade A, and why
org-politics-commands 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 11d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organizational Politics Commands
/stakeholders
View the current stakeholder influence map from memory. Default view shows all mapped stakeholders sorted by power level. Filters narrow to specific positions, power levels, or initiatives. If no map exists, prompts the user to create one via the organizational-alignment-playbook.
Syntax: /stakeholders [--position <filter>] [--power <filter>] [--initiative <name>]
Parameters: --position (champion/supporter/neutral/skeptic/blocker), --power (high/medium/low), --initiative (initiative name in quotes).
Examples:
/stakeholders
/stakeholders --position blocker
/stakeholders --power high
/stakeholders --initiative "Q2 Pivot"
/stakeholders --position champion --initiative "Platform Rewrite"
Related: /power-map, /resistance, /coalition, /context
Errors: No map in memory prompts creation. Invalid filter names return valid options.
/power-map
Generate or refresh the power dynamics map showing formal authority, informal influence, and information flows. Displays existing map from memory and prompts for updates. The --refresh flag forces complete reassessment after organizational changes.
Syntax: /power-map [--initiative <name>] [--refresh]
Parameters: --initiative (scope to specific initiative), --refresh (force reassessment).
Examples:
/power-map
/power-map --initiative "Q2 Pivot"
/power-map --refresh
Related: /stakeholders, /resistance, /diagnose
Errors: No organizational data prompts structure description. Unknown initiative lists available ones.
/resistance
Analyze stakeholder resistance to a specific initiative by running stakeholder-resistance-diagnosis. Identifies all skeptics and blockers on the stakeholder map and diagnoses root cause for each. Outputs per-stakeholder diagnosis, root cause classification, and recommended engagement strategy. Results persist to active memory.
Syntax: /resistance "<initiative-name>"
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.
- 11d ago First seen · 103 lines · 56 tokens per session scan A 32843e1907bd
org-politics-commands is a command published in the GitHub repository fatihguner/foreman (50 stars, last pushed 5d ago), licensed MIT. It adds 56 tokens to every session and 975 once invoked, about $0.0003 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 commands, from other repositories
frappe-gameplan
Treat the task as Frappe Gameplan work.
sdlc
Master orchestrator for the complete 5-phase SDLC pipeline. Runs all phases sequentially with approval gates and handoffs between each phase. Organizes artifacts into handoffs/, docs/, and projects/ directories.
to-issues
Create one Linear issue per slice from an existing scope.json. Run standalone to (re)create issues without rerunning the full Plan phase. Falls back to docs/issues.md if Linear MCP is unavailable.
sdlc-plan
Phase 1 — Plan. Runs product-manager grill-me interview + slice decomposition, then publishes PRD and creates issues. Invokes exactly 1 agent.
arckit.backlog
Generate prioritised product backlog from ArcKit artifacts - convert requirements to user stories, organise into sprints.
arckit.story
Generate comprehensive project story with timeline analysis, traceability, and governance achievements (project).