add-portal

A command for creating a search skill for a local job board. It investigates the job portal, creates the skill's files, and tests a live search before registration.

In plain words
What is it for?
Use it to add job-search support for a portal in your country or language, including researching its structure and trying a real query.
Why use it?
It gives you a guided way to adapt the job-search framework to portals that are not already supported. The generated skill stays in your own project.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/madslorentzen/ai-job-search/add-portal
Clone the repo
git clone --depth 1 https://github.com/MadsLorentzen/ai-job-search

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,266 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03266
Opus 5 $0.00000 $0.01633
Sonnet 5 $0.00000 $0.00653
Haiku 4.5 $0.00000 $0.00327

Measured 2d ago against content hash 7cd254993de0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-portal scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Do reconnaissance before writing any code. Use WebFetch (or `curl` via Bash) on the portal:
Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.claude/commands/add-portal.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/add-portal - Generate a Job-Portal Search Skill for Your Local Market

You are helping the user build a job-portal search skill for a job board in their market. The repo ships worked examples of the pattern (four Danish portals plus the country-agnostic linkedin-search and freehire-search), and the README invites users elsewhere to build equivalents — this command turns that invitation into a guided workflow: investigate the portal, scaffold the skill from the canonical structure, and test-run a live query before registering anything.

The generator is country-agnostic: it works for any portal in any market and language. The skills it produces are typically market-specific and live in the user's fork (per repo policy, country-specific portal skills are not merged upstream — the generator is the upstream feature, its output is yours).

$ARGUMENTS may contain a subcommand, a portal URL, or nothing.

Follow these steps in order.


Step 0: Parse Arguments

  • If $ARGUMENTS contains --list: use Glob with .agents/skills/*/SKILL.md, print a table of installed portal skills (name, market from the description, data source from url-reference.md), and stop.
  • If $ARGUMENTS contains a URL: treat it as the portal URL and carry it into Step 1.
  • Otherwise: start the interview at Step 1.

Step 1: Interview - Portal Basics

Ask the user (skip anything already answered by $ARGUMENTS):

  1. Portal URL - the job board's public site (e.g. https://www.seek.com.au, https://www.stepstone.de).
  2. Skill name - kebab-case, suffixed -search (e.g. seek-search, stepstone-search). Must not collide with an existing folder in .agents/skills/.
  3. Market and language - which country/region the portal covers and what language its postings use. This drives the trigger phrases in SKILL.md (include local-language terms like the Danish skills do: "ledige stillinger", "jobsøgning").
  4. A realistic test query - a job title or skill the user would actually search for, used for the live test in Step 4.

Read the full file on GitHub · 161 lines

Changes

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.

  1. 2d ago First seen · 161 lines · 0 tokens per session scan A 7cd254993de0

Subscribe to this mod's changes

add-portal is a command published in the GitHub repository MadsLorentzen/ai-job-search (39,400 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,266 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.