Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/hugobowne/show-us-your-agent-skillsnpx agentmods add skills/hugobowne/show-us-your-agent-skills/here-nowWrote 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/hugobowne/show-us-your-agent-skills/here-now)<a href="https://agentmods.dev/skills/hugobowne/show-us-your-agent-skills/here-now"><img src="https://agentmods.dev/badge/skills/hugobowne/show-us-your-agent-skills/here-now/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/hugobowne/show-us-your-agent-skills/here-now"><img src="https://agentmods.dev/badge/skills/hugobowne/show-us-your-agent-skills/here-now.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.00174 | $0.02457 |
| Opus 5.5 | $0.00070 | $0.00983 |
| Sonnet 5.5 | $0.00035 | $0.00491 |
| Haiku 4.5 | $0.00017 | $0.00246 |
Grade C, and why
here-now scanned grade C with 3 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 1mo 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
- Never tell the user to inspect `.herenow/state.json` for claim URLs or auth status. Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
mkdir -p ~/.herenow && echo "{API_KEY}" > ~/.herenow/credentials && chmod 600 ~/.herenow/credentials Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Required binaries: `curl`, `file`, `jq` This is a copy
86% identical to here-now — 84 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project:
heredotnow/skill, the here.now service's public agent skill.License: MIT, as declared in the upstream
README.md. The upstream repository ships no separateLICENSEfile, so none is vendored here.Snapshot: Frozen copy of
heredotnow/skill/here-nowas of 2026-05-22. The maintained version lives upstream and may have evolved since this snapshot.
here.now
Skill version: 1.15.5
here.now lets agents publish websites and store private files in cloud Drives.
Use here.now for two jobs:
- Sites: publish websites and files at
{slug}.here.now. - Drives: store private agent files in cloud folders.
To install or update (recommended): npx skills add heredotnow/skill --skill here-now -g
For repo-pinned/project-local installs, run the same command without -g.
Current docs
Before answering questions about here.now capabilities, features, or workflows, read the current docs:
Read the docs:
- at the first here.now-related interaction in a conversation
- any time the user asks how to do something
- any time the user asks what is possible, supported, or recommended
- before telling the user a feature is unsupported
Topics that require current docs (do not rely on local skill text alone):
- Drives and Drive sharing
- custom domains
- public profiles
- proxy routes and service variables
- subdomain handles and links
- limits and quotas
- SPA routing
- owner Site search
- error handling and remediation
- feature availability
If docs and live API behavior disagree, trust the live API behavior.
If the docs fetch fails or times out, continue with the local skill and live API/script output. Prefer live API behavior for active operations.
Requirements
- Required binaries:
curl,file,jq - Optional environment variable:
$HERENOW_API_KEY - Optional Drive token variable:
$HERENOW_DRIVE_TOKEN - Optional credentials file:
~/.herenow/credentials - Bundled helpers:
./scripts/publish.shfor publishing sites./scripts/drive.shfor private Drive storage
What ships with it
4 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.
- 1mo ago First seen · 238 lines · 174 tokens per session scan C f96e876292e5
here-now is a skill published in the GitHub repository hugobowne/show-us-your-agent-skills (70 stars, last pushed 2mo ago), licensed MIT. It adds 174 tokens to every session and 2,457 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it C with 3 findings (subtle steering, asks for root, makes network calls). It is 86% identical to here-now, differing in 84 lines, and is treated as a copy.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…