DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to look up rules across project, vendor, user, and system scopes with Okf Agent Memory

Find a concept in the right layer, with higher-priority scopes shadowing lower ones.

Who it is forA developer who keeps personal style notes and vendor framework rules alongside a project and needs the agent to pick the right one.

The problemGuidance lives in several places, and an agent can pick an outdated or wrong version without a clear precedence order.

The outcomeSearches and lookups return the authoritative concept, with project content overriding vendor, user, and system content.

What you need first

  • A Git repository where the agent works
  • A Go toolchain and make, since the README builds the tool with make build
  • Clone access to github.com/okf-memory/okf-agent-memory

Steps

  1. Run make build to create bin/okf.
  2. Run ./bin/okf search "authentication" to search all scopes with automatic shadowing and priority ranking.
  3. Run ./bin/okf search "routing" --scope vendor to limit the search to vendor packages.
  4. Run ./bin/okf show user:guidelines/style to read a personal concept by its scoped name.
  5. Run ./bin/okf show decisions/auth to read the local project concept, which takes priority over other scopes with the same ID.

Prompt for your agent

Using the okf-memory/okf-agent-memory repo, search for <topic> across all scopes, then show the concept the search ranks first. Report which scope it came from and whether a higher-priority scope shadows any other matching concept. Verify the scope label before using the concept.

Caveat. Vendor packages and the user and system layers only return results if those folders are populated, and the README excerpt does not explain how to install vendor packages.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page