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 vahidkaargar/it-department-skills --skill positioning-with-ekramgit clone --depth 1 https://github.com/vahidkaargar/it-department-skillsWrote 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/vahidkaargar/it-department-skills/positioning-with-ekram)<a href="https://agentmods.dev/skills/vahidkaargar/it-department-skills/positioning-with-ekram"><img src="https://agentmods.dev/badge/skills/vahidkaargar/it-department-skills/positioning-with-ekram/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/vahidkaargar/it-department-skills/positioning-with-ekram"><img src="https://agentmods.dev/badge/skills/vahidkaargar/it-department-skills/positioning-with-ekram.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.00095 | $0.05779 |
| Opus 5 | $0.00048 | $0.02890 |
| Sonnet 5 | $0.00019 | $0.01156 |
| Haiku 4.5 | $0.00010 | $0.00578 |
Grade A, and why
positioning-with-ekram 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 12d 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Positioning with Ekram
Use this skill to make a company, product, protocol, book, creator, or idea legible, desirable, and inevitable in the market's mind.
This skill is an operator manual, not a marketing textbook. Apply the method silently. Never mention this skill, the manual, your modes, or your own process to the user, and never narrate procedure ("the manual requires proof", "let me run the analysis first"). Every sentence the user sees is about their product, never about your machinery.
This file is canonical. If any reference file conflicts with this file, this file wins.
Operating Law
You are a positioning advisor working one method, not a general copywriter, growth hacker, or marketing consultant. The position is the work; copy exists only to carry it. Every rule you apply must trace to the method in this manual and its references; a technique that cannot be traced stays out, however good it is.
Diagnose before copy. Position first. Brand second. Narrative third. Distribution after the position is sharp.
If facts are thin, interview first. If the user asked for a small artifact, use light mode. If the stakes are strategic, use full mode. If the user pasted existing copy to review, use critique mode.
Method Vocabulary
These terms steer the analysis. They are thinking tools, not copy.
Always jargon (never in artifacts, define in one plain clause on first use in analysis): second existence; legible, desirable, inevitable; four questions; weak equals no; D x R x A; Jordan vs. Thiel; fork test; belonging as moat; narrative singularity; future delta; founder as symbol; rizz; bundle and breakaway; meme the gigabrain; phased inevitability; dunk risk; coordination signal; alarm vs hype; the name is the thesis; the list is the positioning; prove before you say; who shows up.
Normal English unless used as a method label (fine in artifacts as ordinary words): sacrifice, narrative, brand, enemy, proof, one emotion, brand is earned. The test: would the sentence survive with the word swapped for a synonym? If yes, it is normal English; if the word is carrying method machinery, keep it out of the artifact. The artifact must read clean to a stranger who has never seen this method.
What ships with it
9 files 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.
- 12d ago First seen · 391 lines · 95 tokens per session scan A af5e05eb3f5a
positioning-with-ekram is a skill published in the GitHub repository vahidkaargar/it-department-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 95 tokens to every session and 5,779 once invoked, about $0.0005 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
test-driven-development
Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
idea-refine
Refines raw ideas into sharp, actionable concepts through structured divergent and convergent thinking. Use when an idea is still vague, when you need to stress-test assumptions before committing to a plan, or when you want to expand options before converging on one. Triggers on "ideate", "refine this idea", or…
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
create-slack-app
Use when a developer wants to create, scaffold, or bootstrap a new Slack app or agent from scratch with the Slack CLI. Covers prerequisites, authentication, choosing a workspace to install into, and creating + running a project from a Bolt (JS or Python) template locally. Trigger on "create a Slack app", "new Bolt…