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 michelgrolet/tars-location-mcp --skill where-was-igit clone --depth 1 https://github.com/michelgrolet/tars-location-mcpWrote 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/michelgrolet/tars-location-mcp/where-was-i)<a href="https://agentmods.dev/skills/michelgrolet/tars-location-mcp/where-was-i"><img src="https://agentmods.dev/badge/skills/michelgrolet/tars-location-mcp/where-was-i/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/michelgrolet/tars-location-mcp/where-was-i"><img src="https://agentmods.dev/badge/skills/michelgrolet/tars-location-mcp/where-was-i.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.00105 | $0.00701 |
| Opus 5 | $0.00053 | $0.00351 |
| Sonnet 5 | $0.00021 | $0.00140 |
| Haiku 4.5 | $0.00011 | $0.00070 |
Grade A, and why
where-was-i 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Where was I
The user has an archive of their own past positions. It is the only thing in the room that knows the answer, and it is cheap to ask. Read it before answering, not after being corrected.
Pick the tool that matches the question
| The question | The tool |
|---|---|
| where am I, is this fix current | current_location |
| what did I do on a date | day |
| every stop over a window, in order | stays |
| which cities, how long in each, how many separate times | cities_visited |
| the same by country | countries_visited |
| where do I spend my time, what was that address | top_places |
| what trips have I taken | trips, then trip for one in full |
| kilometres, flights, days away | travel_stats |
| highest, farthest, longest flight, most cities in a day | records |
| where have I lived | home |
| who was I with | who_was_there |
| anything the above does not shape | location_sql, read-only |
stays, cities_visited, countries_visited, travel_stats and top_places all take either period (today, yesterday, this_week, last_week, this_month, last_month, this_year, last_year, last_N_days, all) or an explicit since/until pair. Prefer the explicit pair whenever the user named real dates.
Empty is not the same as never
The archive is assembled from an export plus a live feed, so it has holes: the months between the day the export was taken and the day the tracker was installed, a phone that was replaced, an app that was uninstalled.
When a tool comes back empty, call location_coverage before saying anything. It reports every gap of two weeks or more, measured from the data. If the window the user asked about sits inside a gap, the answer is "nothing was recorded then", never "you were not there". Those two sentences are not interchangeable and only one of them is honest.
Every windowed answer already carries the period and timezone it used. Keep them when you report: an answer that does not say what it covers is not an answer.
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 · 42 lines · 105 tokens per session scan A b8b82a123912
where-was-i is a skill published in the GitHub repository michelgrolet/tars-location-mcp (0 stars, last pushed 17d ago), licensed MIT. It adds 105 tokens to every session and 701 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, offers to turn Diagnostics on when the project has it…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.