Borrowing it
Nothing to install: this file belongs to suraj-davariya/ai-job-search. 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/suraj-davariya/ai-job-search/main/.agents/skills/example-portal/SKILL.mdgit clone --depth 1 https://github.com/suraj-davariya/ai-job-searchWrote 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/suraj-davariya/ai-job-search/example-portal)<a href="https://agentmods.dev/skills/suraj-davariya/ai-job-search/example-portal"><img src="https://agentmods.dev/badge/skills/suraj-davariya/ai-job-search/example-portal/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/suraj-davariya/ai-job-search/example-portal"><img src="https://agentmods.dev/badge/skills/suraj-davariya/ai-job-search/example-portal.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.00041 | $0.00800 |
| Opus 5 | $0.00020 | $0.00400 |
| Sonnet 5 | $0.00008 | $0.00160 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
example-portal 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Example Portal Adapter — TEMPLATE (copy me)
⚠️ This is a template, not a working portal. Its
cli/returns clearly-labelled example data so you can run it end-to-end and see the contract. To add a real portal, copy this whole directory to.agents/skills/<portal-name>/and implement real fetching incli/index.ts.
Why .agents/skills/ and not .claude/skills/?
Per ADR-0004, structured portal adapters are a Plane-2 extension: each portal is a
self-contained CLI tool that the country-agnostic job-scraper
skill calls out to, with web search (site:<portal>) as the universal fallback. They live
under .agents/skills/ deliberately — that path is not the Claude Code skill
auto-load directory (.claude/skills/), so an adapter is invoked as a CLI (via bun run),
never silently activated as a chat skill. This keeps the core framework clean and lets any
market contribute an adapter without changing core code.
Directory contract (ADR-0004)
.agents/skills/<portal-name>/
├── SKILL.md # this file — trigger keywords + contract
├── cli/
│ ├── package.json # dependencies + start script (Bun/TypeScript)
│ └── index.ts # CLI entry point implementing the contract below
└── url-reference.md # optional — the portal's search-URL patterns
CLI contract
| Runtime | Bun (TypeScript). node/npx tsx also work for this template. |
| Input | CLI flags: --keywords "<terms>", --location "<place>", --date-range <days> |
| Output | A JSON array on stdout, one object per posting: { title, company, location, url, date, snippet } |
| Exit code | 0 on success (even with zero results — emit []), 1 on error (message on stderr) |
The job-scraper skill runs the adapter like:
bun run .agents/skills/<portal-name>/cli/index.ts \
--keywords "data engineer" --location "Remote" --date-range 14
…then parses the JSON array, dedupes against seen_jobs.json, quick-rates fit, and
presents results exactly as it does for web-search hits.
What ships with it
3 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 · 67 lines · 41 tokens per session scan A 0c219541a0dc
example-portal is a skill published in the GitHub repository suraj-davariya/ai-job-search (22 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 800 once invoked, about $0.0002 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 skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.